Triple
T25018322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Army |
E626201
|
entity |
| Predicate | formedForConflict |
P31144
|
FINISHED |
| Object | Franco-Prussian War |
—
|
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: Franco-Prussian War | Statement: [Second Army, formedForConflict, Franco-Prussian War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedForConflict Context triple: [Second Army, formedForConflict, Franco-Prussian War]
-
A.
formedInConflict
chosen
Indicates that an entity came into existence as a direct result of, or during the course of, a specific conflict or war.
-
B.
namedForConflict
Indicates that one entity is named after, or in commemoration of, a specific conflict, war, or battle.
-
C.
reportedConflict
Indicates that one party has formally reported the existence of a conflict involving another party or situation.
-
D.
raisedForConflict
Indicates that an issue, concern, or case has been formally brought up due to a conflict between parties or conditions.
-
E.
ledToConflict
Indicates that one event, action, or condition caused or significantly contributed to the emergence or escalation of a conflict between parties.
- 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_69e2ff27755881908490178e83701160 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 18, 2026, 6:06 a.m.