Triple
T21923720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trojan plain |
E541384
|
entity |
| Predicate | timePeriodOfMythicEvents |
P136405
|
FINISHED |
| Object | mythic age of heroes |
—
|
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: mythic age of heroes | Statement: [Trojan plain, timePeriodOfMythicEvents, mythic age of heroes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfMythicEvents Context triple: [Trojan plain, timePeriodOfMythicEvents, mythic age of heroes]
-
A.
timeInMyth
Indicates that an entity exists or occurs during a specific time period within a mythological narrative or tradition.
-
B.
hasMythicTimeframe
chosen
Indicates that the relationship associates something with a timeframe situated in mythic or legendary, rather than historical, time.
-
C.
hasMythicEvent
Indicates that an entity is associated with, involves, or features a significant mythic or legendary event.
-
D.
timePeriodEvent
Indicates that an event occurs, is scheduled, or is valid within a specified time period.
-
E.
timePeriodMechanic
Indicates a temporal relationship in which a particular mechanic, process, or method is valid, active, or applicable during a specified time period.
- 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_69e0c47d74488190a15119108794a307 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1233dc504819083ee27e253805189 |
completed | April 28, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:45 p.m.