Triple
T21199435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amphimachus |
E522412
|
entity |
| Predicate | relationToHeracles |
P123069
|
FINISHED |
| Object | maternal uncle |
—
|
LITERAL 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: maternal uncle | Statement: [Amphimachus, relationToHeracles, maternal uncle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToHeracles Context triple: [Amphimachus, relationToHeracles, maternal uncle]
-
A.
relationshipToHeracles
chosen
Indicates the specific familial or social relationship that an entity has to Heracles.
-
B.
relationToOdysseus
Indicates the specific familial, social, or narrative relationship that one entity has to Odysseus.
-
C.
childWithHeracles
Indicates that one entity is a child whose father is Heracles.
-
D.
relationshipToDeianira
Indicates a specified type of relationship that one entity has to Deianira, such as familial, romantic, or social connection.
-
E.
relationshipToPriamAndHecuba
Indicates a familial or relational connection that an entity has specifically to both Priam and Hecuba.
- F. None of above.
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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7342fe3a08190b7ed2cadf60091a8 |
completed | April 21, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:17 p.m.