Triple
T16296786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camelopardalis |
E395667
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Perseus |
E23577
|
NE 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: Perseus | Statement: [Camelopardalis, locatedNear, Perseus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Perseus Context triple: [Camelopardalis, locatedNear, Perseus]
-
A.
Perseus
chosen
Perseus is a legendary Greek hero famed for slaying the Gorgon Medusa and rescuing Andromeda.
-
B.
Perseus (son of Nestor)
Perseus is a minor figure in Greek mythology, known primarily as one of the many sons of the Pylian king Nestor.
-
C.
Heracles
Heracles is a legendary hero of Greek mythology renowned for his superhuman strength and his completion of the Twelve Labors.
-
D.
Νέστωρ
Νέστωρ is a wise and elderly king of Pylos in Greek mythology, renowned for his counsel during the Trojan War and his role in Homer's epics.
-
E.
Melicertes
Melicertes is a figure in Greek mythology who, after his death and transformation at sea, became the sea god Palaemon associated with sailors and harbors.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e2dcdac819083918f0964dd5666 |
completed | April 17, 2026, 4:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a001f9b42248190a3c8c2647a42aeb9 |
completed | May 10, 2026, 6:03 a.m. |
Created at: April 10, 2026, 5:06 a.m.