Triple
T20480435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titan |
E502435
|
entity |
| Predicate | hasMember |
P10
|
FINISHED |
| Object | Helios |
—
|
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: Helios | Statement: [Titan, hasMember, Helios]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Helios Context triple: [Titan, hasMember, Helios]
-
A.
Helios
chosen
Helios is the personification of the sun in ancient Greek mythology, often depicted driving a chariot across the sky each day.
-
B.
Ηλιοκλής
Ηλιοκλής is the Greek name of Heliocles II, a little-known Indo-Greek king who ruled parts of northwestern South Asia in the late Hellenistic period.
-
C.
Helian
Helian is a Chinese surname and given name of Xianbei origin, historically associated with rulers of the Hu Xia dynasty during the Sixteen Kingdoms period.
-
D.
Phoebus
Phoebus is a poetic name for the Greek god Apollo, emphasizing his radiant, sun-associated and light-bringing aspects.
-
E.
Phoebus
Phoebus is a dashing and principled captain of the guard who becomes a key ally and love interest in the story of The Hunchback of Notre Dame.
- 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_69e0b4af32848190aea80682b44d5d6e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69b56dd248190b6bc4e513aff3c9c |
completed | April 20, 2026, 9:32 p.m. |
Created at: April 16, 2026, 11:34 a.m.