Triple
T25751830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cross of Valour (Greece) |
E648485
|
entity |
| Predicate | conflictAwardedIn |
P150618
|
FINISHED |
| Object | First World 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: First World War | Statement: [Cross of Valour (Greece), conflictAwardedIn, First World War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictAwardedIn Context triple: [Cross of Valour (Greece), conflictAwardedIn, First World War]
-
A.
conflictsAwardedIn
chosen
Indicates that an award or recognition was given in the context of a specific conflict or set of conflicts.
-
B.
conflictOfFirstAwards
Indicates that there is a conflict or discrepancy between the initial awards or first recognitions associated with the related entities.
-
C.
alsoAwardedIn
Indicates that the same award or recognition was given in an additional time, place, or context beyond the primary one.
-
D.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
E.
awardedDuring
Indicates that an award or honor was given to an entity within a specified time period or event.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fd7ef3c48190b5f1b3b4e9cecb2b |
completed | May 2, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 4:35 a.m.