Triple
T31965435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flandry series |
E816161
|
entity |
| Predicate | chronologicalPlacementInTechnicHistory |
P18401
|
FINISHED |
| Object | late era |
—
|
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 era | Statement: [Flandry series, chronologicalPlacementInTechnicHistory, late era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalPlacementInTechnicHistory Context triple: [Flandry series, chronologicalPlacementInTechnicHistory, late era]
-
A.
chronologyOf
Indicates that one entity represents the temporal ordering, sequence, or historical timeline of events or states associated with another entity.
-
B.
chronologicallyClassifiedAs
chosen
Indicates that something is assigned to or placed within a specific time period or chronological category.
-
C.
chronologyIn
Indicates that one event or temporal entity occurs within the chronological scope or timeframe defined by another.
-
D.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
-
E.
chronologyIncludes
Indicates that a broader chronological sequence or timeline encompasses a specific time span, event, or period as part of it.
- 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: May 1, 2026, 12:09 a.m.