Triple
T37096385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Age of Empires II |
E918574
|
entity |
| Predicate | originalEngine |
P205723
|
FINISHED |
| Object | Genie Engine |
E1853917
|
NE 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: Genie Engine | Statement: [Age of Empires II, originalEngine, Genie Engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalEngine Context triple: [Age of Empires II, originalEngine, Genie Engine]
-
A.
originalEngineType
Indicates the type or category of engine that an entity was initially or first equipped with.
-
B.
originalEngineModel
Indicates that one engine is the original or initial model from which another engine or engine variant is derived.
-
C.
originOfEngine
Indicates the source or place from which an engine originates or is produced.
-
D.
originatesFromEngine
Indicates that something has its source, cause, or production in a particular engine.
-
E.
firstGenerationEngine
Indicates that the engine belongs to the first generation in a series of engine designs or development iterations.
- F. None of above. chosen
Provenance (5 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3efdd08da481909aa66f655cf0c6c3 |
completed | June 26, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:14 p.m.