Triple
T18694256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danaus |
E457074
|
entity |
| Predicate | grandfatherOf |
P979
|
FINISHED |
| Object | Abas |
—
|
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: Abas | Statement: [Danaus, grandfatherOf, Abas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Abas Context triple: [Danaus, grandfatherOf, Abas]
-
A.
Abas
chosen
Abas is a figure in Greek mythology known primarily as the son of Hypermnestra and a king of Argos in some traditions.
-
B.
Abbasanta
Abbasanta is a small town in central Sardinia, Italy, known for its proximity to important Nuragic archaeological sites and its traditional rural character.
-
C.
Abisare
Abisare was an early 2nd-millennium BCE king of the ancient Mesopotamian city-state of Larsa, known for consolidating its power in southern Babylonia.
-
D.
Abasár
Abasár is a village in northern Hungary known for its wine production and location near the Mátra Mountains.
-
E.
Abis
Abis is a standardized GSM interface that connects a base transceiver station (BTS) to its base station controller (BSC) for managing radio resources and signaling.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562e66a188190801fd95f9be26042 |
completed | April 19, 2026, 11:19 p.m. |
Created at: April 10, 2026, 11:49 a.m.