Triple
T37776033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dewoitine D.520 |
E941688
|
entity |
| Predicate | usedAfterArmistice |
P198935
|
FINISHED |
| Object | by Vichy French forces |
—
|
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: by Vichy French forces | Statement: [Dewoitine D.520, usedAfterArmistice, by Vichy French forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAfterArmistice Context triple: [Dewoitine D.520, usedAfterArmistice, by Vichy French forces]
-
A.
usedAfterWar
Indicates that an entity came into use only after a specific war or conflict had ended.
-
B.
opponentAfterArmistice
Indicates that one entity is the opponent of another in the period following an armistice.
-
C.
statusOfArmistice
Indicates the current condition or standing of an armistice agreement between parties.
-
D.
signedAfterArmisticeWith
Indicates that one party formally signed an agreement or document after an armistice had already been concluded with another party.
-
E.
hasArmistice
Indicates a formal agreement between opposing parties to stop active hostilities, typically marking a ceasefire or suspension of fighting.
- 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_69f76ee4431881908f87e8892a9f39f3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff14d596e88190be5263b7f96a96cd |
completed | May 9, 2026, 11:04 a.m. |
| PD | Predicate disambiguation | batch_69ff13f0208081909369aeb3b77a6b1f |
completed | May 9, 2026, 11:01 a.m. |
| PDg | Predicate description generation | batch_69ff14d4dfc48190bc9fba2384988a98 |
completed | May 9, 2026, 11:04 a.m. |
Created at: May 3, 2026, 4:19 p.m.