Triple
T21335921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoenix |
E526045
|
entity |
| Predicate | sibling |
P363
|
FINISHED |
| Object | Cadmus |
—
|
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: Cadmus | Statement: [Phoenix, sibling, Cadmus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cadmus Context triple: [Phoenix, sibling, Cadmus]
-
A.
Cadmus
chosen
Cadmus is a legendary Phoenician prince in Greek mythology, famed as the founder and first king of Thebes and the bringer of the alphabet to the Greeks.
-
B.
Erichthonius
Erichthonius is a legendary early king of Dardania in Greek mythology, often regarded as an ancestor of the Trojan royal line.
-
C.
Pheneus
Pheneus was an ancient Arcadian city in the northeastern Peloponnese, known from Greek mythology and classical geography.
-
D.
Cranaus
Cranaus is a legendary early king of Athens in Greek mythology, often associated with the city's primeval history before the time of more famous rulers like Erechtheus and Theseus.
-
E.
Cretheus
Cretheus is a figure in Greek mythology, a king of Iolcus and ancestor of the hero Jason.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b51c33048190ab27cede74ef798c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e898d7d8b88190b2f346e4592b3bc5 |
completed | April 22, 2026, 9:46 a.m. |
Created at: April 16, 2026, 4:43 p.m.