Triple
T31140095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molossus |
E793756
|
entity |
| Predicate | timeOfMythologicalTradition |
P20414
|
FINISHED |
| Object | Classical Greece |
—
|
NE NERFINISHED |
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: Classical Greece | Statement: [Molossus, timeOfMythologicalTradition, Classical Greece]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfMythologicalTradition Context triple: [Molossus, timeOfMythologicalTradition, Classical Greece]
-
A.
timeInMyth
chosen
Indicates that an entity exists or occurs during a specific time period within a mythological narrative or tradition.
-
B.
chronologyWithinMythos
Indicates that one event, story, or element occurs at a specific position or order within the internal timeline of a particular mythos or fictional universe.
-
C.
timeInTradition
Indicates the temporal context or period in which a given tradition is practiced, observed, or relevant.
-
D.
mythologicalContent
Indicates that the subject contains, references, or is associated with myths, mythological narratives, or myth-based elements.
-
E.
mythologicalStartDateInGregorian
Indicates the date, expressed in the Gregorian calendar, on which a mythological event, era, or figure is considered to have begun.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: April 29, 2026, 9:05 p.m.