Triple
T26076496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athens (through the story of Theseus) |
E657699
|
entity |
| Predicate | mythicKing |
P73488
|
FINISHED |
| Object | Aegeus |
—
|
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: Aegeus | Statement: [Athens (through the story of Theseus), mythicKing, Aegeus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mythicKing Context triple: [Athens (through the story of Theseus), mythicKing, Aegeus]
-
A.
notableMythicKing
chosen
Indicates that the subject is recognized as a prominent or distinguished king within myth or legend.
-
B.
mythologicalQueen
Indicates that one entity is a queen who exists within mythology, legend, or folklore rather than historical reality.
-
C.
mythicAttribute
Indicates that one entity possesses or is characterized by a legendary, mythical, or folklore-based quality, power, or status in relation to another.
-
D.
kingOf
Indicates that one entity holds the position or role of king in relation to another entity, typically a territory, people, or domain.
-
E.
mythologicalPrincess
Indicates that the subject is a princess who exists within mythology, legend, or folklore rather than in historical reality.
- 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f606cf938c8190aa96a095c824367e |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 7:34 p.m.