Triple
T27501934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medal of Honor: Airborne score |
E694176
|
entity |
| Predicate | setInConflictOfGame |
P56733
|
FINISHED |
| Object | World War II |
—
|
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 II | Statement: [Medal of Honor: Airborne score, setInConflictOfGame, World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setInConflictOfGame Context triple: [Medal of Honor: Airborne score, setInConflictOfGame, World War II]
-
A.
settingOfConflict
chosen
Indicates the location or context in which a conflict between entities takes place.
-
B.
settingConflict
Indicates a conflict or incompatibility between two settings, configurations, or environmental conditions.
-
C.
settingWithinPlay
Indicates that a particular setting (such as a location or environment) occurs within and is part of a specific play.
-
D.
allegedStartGame
Indicates that an entity is claimed or reported, but not confirmed, to have initiated a game.
-
E.
subConflict
Indicates that one conflict is a component, phase, or subordinate part of a larger overarching conflict.
- 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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 1:11 p.m.