Triple
T38634361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No Russian |
E937538
|
entity |
| Predicate | chronologicalPositionInCampaign |
P198097
|
FINISHED |
| Object | fourth 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: fourth mission | Statement: [No Russian, chronologicalPositionInCampaign, fourth mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalPositionInCampaign Context triple: [No Russian, chronologicalPositionInCampaign, fourth mission]
-
A.
chronologicalPositionInGame
Indicates the specific point or order in time at which an event, action, or state occurs within the progression of a game.
-
B.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
-
C.
chronologicalPositionInLabors
Indicates the specific order or sequence in which a given labor occurs within a defined series of labors.
-
D.
chronologicalPositionInFamilySaga
Indicates the relative order in which an event, episode, or member appears within the timeline of a family saga.
-
E.
chronologicalPositionInEpicCycle
Indicates the relative order or placement of an event, episode, or work within the overall sequence of an epic cycle.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69fec8adaa308190a9a276f8c36f15f0 |
completed | May 9, 2026, 5:39 a.m. |
Created at: May 3, 2026, 4:32 p.m.