Triple
T35020037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tirailleurs sénégalais |
E1010167
|
entity |
| Predicate | significantInConflict |
P106814
|
FINISHED |
| Object | World War I |
—
|
NE NERFINISHED |
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: World War I | Statement: [Tirailleurs sénégalais, significantInConflict, World War I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantInConflict Context triple: [Tirailleurs sénégalais, significantInConflict, World War I]
-
A.
mentionsConflict
Indicates that one entity refers to or discusses a dispute, disagreement, or conflict involving another entity.
-
B.
significantDuringConflict
chosen
Indicates that something plays an important or influential role specifically in the context of a conflict or dispute.
-
C.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
D.
formedInConflict
Indicates that an entity came into existence as a direct result of, or during the course of, a specific conflict or war.
-
E.
notableInternalConflict
Indicates a significant or historically important internal conflict occurring within an entity, such as a country, organization, or group.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:01 p.m.