Triple
T5182123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gyes |
E116944
|
entity |
| Predicate | mythicEra |
P20831
|
FINISHED |
| Object | age of the 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 the Titans | Statement: [Gyes, mythicEra, age of the Titans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mythicEra Context triple: [Gyes, mythicEra, age of the Titans]
-
A.
eraOfMyth
chosen
Indicates a temporal relationship where an event, story, or phenomenon belongs to or takes place during a mythological or legendary era.
-
B.
mythicReputation
Indicates a reputation or renown of legendary, larger-than-life status associated with an entity.
-
C.
fictionalEra
Indicates the time period or age within a fictional or imaginary setting in which an entity exists or an event occurs.
-
D.
mythologicalGeneration
Indicates a generational relationship in mythology, where one mythological being or group descends from or follows another in a lineage or succession.
-
E.
timeInMyth
Indicates that an entity exists or occurs during a specific time period within a mythological narrative or tradition.
- 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_69bd446140f08190becb93c61158f27f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd799bc58c819098a8e91e21baaef4 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b7e8b4819092ec3965e11f2dea |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:45 p.m.