Triple
T29077758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Final Fight 3 |
E735986
|
entity |
| Predicate | basedOnEngineType |
P56323
|
FINISHED |
| Object | 2D sprite-based engine |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 2D sprite-based engine | Statement: [Final Fight 3, basedOnEngineType, 2D sprite-based engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnEngineType Context triple: [Final Fight 3, basedOnEngineType, 2D sprite-based engine]
-
A.
engineTypeUsed
chosen
Indicates that a particular type of engine is employed or utilized in relation to a specified entity or system.
-
B.
engineTypeIncluded
Indicates that a specified engine type is included as part of, or supported within, another entity or configuration.
-
C.
originalEngineType
Indicates the type or category of engine that an entity was initially or first equipped with.
-
D.
typicalEngineCharacteristic
Indicates that the specified property or feature is a characteristic commonly or typically associated with the given engine.
-
E.
engineTypeBuilt
Indicates that a specific type of engine has been constructed or manufactured by a particular entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f077e9b0a48190bb79548279cb7f64 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: April 28, 2026, 10:24 a.m.