Triple
T37487000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No Fighting in the War Room |
E931558
|
entity |
| Predicate | positionInCampaign |
P198097
|
FINISHED |
| Object | late-game mission |
—
|
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: late-game mission | Statement: [No Fighting in the War Room, positionInCampaign, late-game mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInCampaign Context triple: [No Fighting in the War Room, positionInCampaign, late-game mission]
-
A.
positionOnBallot
Indicates the specific ordered place that a candidate or option occupies on an election ballot.
-
B.
chronologicalPositionInCampaign
chosen
Indicates the position or order of an event, action, or element within the overall sequence of a campaign.
-
C.
positionInNominationProcess
Indicates the specific stage or rank an entity holds within a defined nomination process.
-
D.
locationOfCampaign
Indicates the place or geographic area where a particular campaign is conducted or based.
-
E.
partyPositionIn
Indicates the role or stance that a party holds within a particular context, such as an event, organization, or situation.
- 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_69f76ec382248190b47844df596123c6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffe12ee59c8190bc7da386e6d5332d |
completed | May 10, 2026, 1:36 a.m. |
| PD | Predicate disambiguation | batch_69ffe0a138bc8190a3d4b48cd579e985 |
completed | May 10, 2026, 1:34 a.m. |
Created at: May 3, 2026, 4:17 p.m.