Triple
T10895981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polyxo |
E257310
|
entity |
| Predicate | father |
P120
|
FINISHED |
| Object | Atlas |
E18778
|
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: Atlas | Statement: [Polyxo, father, Atlas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Atlas Context triple: [Polyxo, father, Atlas]
-
A.
Atlas
chosen
Atlas is a Titan from Greek mythology best known for bearing the weight of the heavens on his shoulders as punishment from the gods.
-
B.
Atlas
Atlas is a family of American expendable launch vehicles originally developed from a ballistic missile program and widely used to place satellites and spacecraft into orbit.
-
C.
Atlas
Atlas is a professional Mexican football club based in Guadalajara, Jalisco, known for its historic presence in Liga MX.
-
D.
Atlas
Atlas is one of the two cooperative testing robots in the puzzle-platform video game Portal 2, known for assisting in solving test chambers designed by GLaDOS.
-
E.
Atlas
Atlas is a comprehensive digital mapping and geographic information system platform that serves as the foundational framework for applications like Electric Atlas (2024).
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75d022f4c81909cd9ea27a9f0cd32 |
completed | April 9, 2026, 8:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e216b417bc8190b35477e9d363a289 |
completed | April 17, 2026, 11:17 a.m. |
Created at: April 8, 2026, 9:21 p.m.