Triple
T19120424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kerbogha of Mosul |
E468026
|
entity |
| Predicate | armyComposition |
P6154
|
FINISHED |
| Object | Turkic troops |
—
|
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: Turkic troops | Statement: [Kerbogha of Mosul, armyComposition, Turkic troops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armyComposition Context triple: [Kerbogha of Mosul, armyComposition, Turkic troops]
-
A.
typeOfTroops
chosen
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
B.
orderOfBattle
Indicates the structured arrangement and hierarchical organization of military forces and units for a specific operation or engagement.
-
C.
USForceStrength
Indicates the level or magnitude of military forces deployed or available by the United States in a given context.
-
D.
orderOfBattleFeature
Indicates a specific structural or organizational characteristic associated with a military order of battle.
-
E.
militaryEquivalence
Indicates that two or more entities possess comparable military capabilities, strength, or strategic power such that neither holds a clear military advantage over the other.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3c921d4819092e2ae237bf85978 |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.