Triple
T29304869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleon I |
E743063
|
entity |
| Predicate | timePeriodInCanon |
P302
|
FINISHED |
| Object | 12,000th year of the Galactic Era (approximate) |
—
|
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: 12,000th year of the Galactic Era (approximate) | Statement: [Cleon I, timePeriodInCanon, 12,000th year of the Galactic Era (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodInCanon Context triple: [Cleon I, timePeriodInCanon, 12,000th year of the Galactic Era (approximate)]
-
A.
timeInMyth
Indicates that an entity exists or occurs during a specific time period within a mythological narrative or tradition.
-
B.
timePeriodInspiredBy
Indicates that a given time period was influenced or shaped by another time period, event, or era.
-
C.
legendaryPeriod
Indicates a time span associated with legends or mythic events rather than strictly historical chronology.
-
D.
historicalPeriodOfCanonization
Indicates the historical time period during which an entity was formally canonized or officially recognized as a saint or equivalent.
-
E.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 28, 2026, 1:12 p.m.