Triple
T13467841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tinge |
E311548
|
entity |
| Predicate | spouse |
P13
|
FINISHED |
| Object | Antaeus |
E79287
|
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: Antaeus | Statement: [Tinge, spouse, Antaeus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Antaeus Context triple: [Tinge, spouse, Antaeus]
-
A.
Antaeus
chosen
Antaeus is a giant in Greek mythology, famed for drawing his strength from contact with the earth and being defeated by Heracles.
-
B.
Ancaeus
Ancaeus is a figure in Greek mythology, often depicted as a bold but ill-fated hero and Argonaut who met his death during the legendary Calydonian Boar Hunt.
-
C.
Triopas
Triopas is a figure from Greek mythology, traditionally regarded as a king and ancestor within certain heroic lineages.
-
D.
Typhoeus
Typhoeus is a monstrous serpentine giant from Greek mythology, often depicted as a fearsome adversary of Zeus and a symbol of chaotic natural forces.
-
E.
Onchestus
Onchestus was an ancient Boeotian town known for its sanctuary of Poseidon and its association with the Boeotian League.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf101a1081909f2aba6da47baacc |
completed | April 12, 2026, 2:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f74629f1408190b54194fe794be39a |
completed | May 3, 2026, 12:57 p.m. |
Created at: April 9, 2026, 9:42 p.m.