Triple
T35012342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psijic Order |
E1009965
|
entity |
| Predicate | foundedInUniverseEra |
P179545
|
FINISHED |
| Object | First 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: First Era | Statement: [Psijic Order, foundedInUniverseEra, First Era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedInUniverseEra Context triple: [Psijic Order, foundedInUniverseEra, First Era]
-
A.
foundedInFictionalYear
Indicates that an entity was established or created in a year that exists only within a fictional or imaginary timeline, rather than in real-world history.
-
B.
fictionalUniverseDebutYear
Indicates the calendar year in which a fictional universe was first introduced or debuted in any medium.
-
C.
eraOfFoundation
chosen
Indicates the specific historical era or time period during which an entity was founded.
-
D.
timeOfInUniverseCreation
Indicates the specific time at which the universe itself was created within a given narrative or cosmological framework.
-
E.
foundedInOrBefore
Indicates that the founding of one entity occurred in a specified year or any earlier year.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fee691952c8190822da83e46311d1d |
completed | May 9, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69fee62f285c8190a625562a9b80526e |
completed | May 9, 2026, 7:45 a.m. |
Created at: May 3, 2026, 4:01 p.m.