Triple
T36953969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Age of Empires II: The Conquerors |
E914142
|
entity |
| Predicate | addsUnit |
P187229
|
FINISHED |
| Object | Conquistador |
—
|
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: Conquistador | Statement: [Age of Empires II: The Conquerors, addsUnit, Conquistador]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsUnit Context triple: [Age of Empires II: The Conquerors, addsUnit, Conquistador]
-
A.
associatedWithUnit
Indicates that one entity has a connection, linkage, or affiliation with a particular unit (such as a division, department, or organizational subunit).
-
B.
definesUnit
Indicates that one entity specifies the measurement unit or standard by which the value or quantity of another entity is expressed.
-
C.
hasUnitIn
Indicates that one entity is contained or measured within another as a unit, specifying a unit-of-measure or component relationship.
-
D.
associatedUnitType
Indicates that one entity is linked to or characterized by a particular type or category of unit.
-
E.
authorizedUnit
Indicates that one entity is officially permitted or empowered to act on behalf of, or perform certain actions for, another entity or system.
- F. None of above. chosen
Provenance (4 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb34e4906c8190abb1c293fb84329a |
completed | May 6, 2026, 12:32 p.m. |
Created at: May 3, 2026, 4:13 p.m.