Triple
T7249509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aethra |
E156559
|
entity |
| Predicate | siblingOf |
P363
|
FINISHED |
| Object | Metis |
E24190
|
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: Metis | Statement: [Aethra, siblingOf, Metis]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Metis Context triple: [Aethra, siblingOf, Metis]
-
A.
Metis
Metis is a small inner moon of Jupiter that orbits close to the planet and helps supply material to its main ring.
-
B.
Metis
chosen
Metis is a Titaness in Greek mythology associated with wisdom and cunning, best known as the mother of Athena.
-
C.
Kaska
Kaska is an Athabaskan Indigenous language traditionally spoken by the Kaska Dena people of northern Canada, primarily in the Yukon and northern British Columbia.
-
D.
Iolkos
Iolkos was an ancient city in Thessaly, Greece, traditionally known as the homeland of Jason and the starting point of the Argonauts’ voyage in Greek mythology.
-
E.
Ainos
Ainos was a medieval port city and strategic stronghold on the northern Aegean coast, historically contested by Byzantine, Genoese, and Ottoman powers.
- 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_69c68827b5e481908dc05e145b2c92d4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea77a3588190accf31860170f052 |
completed | March 27, 2026, 8:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7d3a2ba748190890c2980ca4a8ecd |
completed | March 28, 2026, 1:12 p.m. |
Created at: March 27, 2026, 2:56 p.m.