Triple
T7021369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argonauts |
E162831
|
entity |
| Predicate | hasMember |
P10
|
FINISHED |
| Object | Lynceus |
E581563
|
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: Lynceus | Statement: [Argonauts, hasMember, Lynceus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lynceus Context triple: [Argonauts, hasMember, Lynceus]
-
A.
Lynceus
chosen
Lynceus is a figure in Greek mythology renowned as one of the Argonauts, famed for his exceptionally keen eyesight.
-
B.
Proetus
Proetus is a king in Greek mythology, often associated with the city of Tiryns and known for his conflicts with his twin brother Acrisius and his role in the story of Bellerophon.
-
C.
Aethlius
Aethlius is a figure in Greek mythology, often regarded as an early king of Elis and associated with the lineage of heroic rulers.
-
D.
Phorcydes
Phorcydes is a primordial sea-deity figure from Greek mythology, often associated with ancient oceanic powers and monstrous offspring.
-
E.
Catreus
Catreus is a figure in Greek mythology, a son of King Minos of Crete whose tragic fate is tied to a prophecy that he would be killed by one of his own children.
- 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_69c6885b26248190a857541e3d10e299 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e1ec34a48190b64cafb94e2f8706 |
completed | March 27, 2026, 8 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7757686bc819089f6749e43bbb89d |
completed | March 28, 2026, 6:30 a.m. |
Created at: March 27, 2026, 2:35 p.m.