Triple
T950539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matthew Ridgway |
E20509
|
entity |
| Predicate | startTimeSupremeAlliedCommanderEurope |
P11103
|
FINISHED |
| Object | 1952 |
—
|
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: 1952 | Statement: [Matthew Ridgway, startTimeSupremeAlliedCommanderEurope, 1952]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeSupremeAlliedCommanderEurope Context triple: [Matthew Ridgway, startTimeSupremeAlliedCommanderEurope, 1952]
-
A.
overallAlliedCommander
Indicates that one entity serves as the highest-ranking commander with ultimate authority over all allied forces associated with the other entity.
-
B.
commandersSide
Indicates that one entity is on the same side, faction, or team as the commander in a conflict or competitive context.
-
C.
commanderUnitedStates
Indicates that one entity serves as the commander of a United States military or governmental unit, mission, or operation.
-
D.
hasCommander
Indicates that one entity serves as the commanding officer or leader of another entity.
-
E.
notableCommanderStart
chosen
Indicates the point in time or event at which a notable commander’s leadership or command role begins in relation to the subject.
- 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_69a493b0f2fc81908cd227480a5356a1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3d62e408190855b2883407f6c6b |
completed | March 1, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a045308190ab94f3adab40db8d |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.