Triple
T206854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iapetus |
E4626
|
entity |
| Predicate | mythologicalEra |
P5250
|
FINISHED |
| Object | age of Titans |
—
|
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: age of Titans | Statement: [Iapetus, mythologicalEra, age of Titans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mythologicalEra Context triple: [Iapetus, mythologicalEra, age of Titans]
-
A.
mythologicalEvent
Indicates an event or occurrence that takes place within mythological narratives or traditions, often involving gods, heroes, or supernatural phenomena.
-
B.
hasCosmogony
Indicates that an entity is associated with, or characterized by, a particular account or doctrine of the origin and development of the universe or cosmos.
-
C.
historicalEraUsheredIn
Indicates the historical era or period that was initiated or brought about as a result of a particular event, action, or entity.
-
D.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
-
E.
eraOfSignificance
chosen
Indicates the historical period or timeframe during which an entity was particularly important, influential, or noteworthy.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e2aba74819093eddd8d820260c0 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b4c7f908190876c1041db52dffc |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.