Triple
T5143664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federation Standard |
E116017
|
entity |
| Predicate | timePeriodOfUseInUniverse |
P12795
|
FINISHED |
| Object | 22nd century |
—
|
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: 22nd century | Statement: [Federation Standard, timePeriodOfUseInUniverse, 22nd century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfUseInUniverse Context triple: [Federation Standard, timePeriodOfUseInUniverse, 22nd century]
-
A.
inUniverseAge
Indicates the age of an entity as measured within the timeline or continuity of a specific fictional or defined universe.
-
B.
timeExistence
chosen
Indicates the period or duration during which an entity exists or is valid.
-
C.
cosmicDurationType
Indicates the type or category of a time duration in a cosmic or astronomical context (e.g., epochs, eras, or other large-scale time spans).
-
D.
durationOfUse
Indicates the length of time for which something is used or remains in use.
-
E.
timeInSpace
Indicates the amount of time an entity has spent in outer space.
- 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_69bd4446c0e08190a7c29dc74976bf03 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd78d7f4d081908d59adcd86f52f1d |
completed | March 20, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69bd77ae2f10819098bb8939106e1281 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:43 p.m.