Triple
T31965179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ensign Flandry |
E816154
|
entity |
| Predicate | chronologicalPositionInFlandrySaga |
P193667
|
FINISHED |
| Object | early |
—
|
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: early | Statement: [Ensign Flandry, chronologicalPositionInFlandrySaga, early]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalPositionInFlandrySaga Context triple: [Ensign Flandry, chronologicalPositionInFlandrySaga, early]
-
A.
chronologicalPositionInFamilySaga
Indicates the relative order in which an event, episode, or member appears within the timeline of a family saga.
-
B.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
-
C.
chronologicalPositionAmongPortrayals
Indicates the relative order in time in which one portrayal occurs compared to other portrayals of the same subject.
-
D.
chronologicalPositionInEpicCycle
Indicates the relative order or placement of an event, episode, or work within the overall sequence of an epic cycle.
-
E.
chronologicalPositionInDune
Indicates the relative order or placement of something within the chronological sequence of events in the Dune series.
- 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
| PDg | Predicate description generation | batch_69fd4f38728c8190b3271abc80882cfb |
completed | May 8, 2026, 2:49 a.m. |
Created at: May 1, 2026, 12:09 a.m.