Triple
T20572812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conquest of Baghdad (1534) |
E505143
|
entity |
| Predicate | typeOfGain |
P114735
|
FINISHED |
| Object | territorial expansion |
—
|
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: territorial expansion | Statement: [Conquest of Baghdad (1534), typeOfGain, territorial expansion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfGain Context triple: [Conquest of Baghdad (1534), typeOfGain, territorial expansion]
-
A.
gainedBy
Indicates that something comes to possess, obtain, or receive something else as a result of an action, process, or event.
-
B.
typicalGainType
chosen
Indicates the usual or characteristic type of gain associated with an entity, such as the standard way value or profit is typically obtained.
-
C.
gainedFrom
Indicates that something is obtained, acquired, or derived as a result of a specified source or cause.
-
D.
gained
Indicates that one entity has come to possess, acquire, or increase in something (such as an object, quality, or amount) relative to another point or state.
-
E.
typeOfIncentive
Indicates the specific kind or category of incentive associated with an entity or action.
- 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_69e0b4b721588190993ac7b0a9be2736 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a906f0508190ac698233738f4452 |
completed | April 20, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:39 a.m.