Triple
T31965154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ensign Flandry |
E816154
|
entity |
| Predicate | fictionalEmpire |
P157633
|
FINISHED |
| Object | Terran Empire |
—
|
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: Terran Empire | Statement: [Ensign Flandry, fictionalEmpire, Terran Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalEmpire Context triple: [Ensign Flandry, fictionalEmpire, Terran Empire]
-
A.
imaginaryEmpire
chosen
Indicates a relationship where an entity rules over or belongs to an empire that exists only in imagination, fiction, or conceptual thought rather than in reality.
-
B.
fictionalGalaxy
Indicates that something exists within, originates from, or is associated with a galaxy that is imaginary or not part of the real universe.
-
C.
fictionalUniverse
Indicates that two entities exist within, or are associated with, the same fictional universe or narrative setting.
-
D.
fictionalKingdom
Indicates that an entity is a kingdom that exists only in fiction or imaginative works, rather than in real-world history.
-
E.
fictionalEra
Indicates the time period or age within a fictional or imaginary setting in which an entity exists or an event occurs.
- 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_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: May 1, 2026, 12:09 a.m.