Triple
T24058358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theseus and the Amazons |
E595871
|
entity |
| Predicate | narrativeRoleOfTheseus |
P154700
|
FINISHED |
| Object | Athenian hero and king |
—
|
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: Athenian hero and king | Statement: [Theseus and the Amazons, narrativeRoleOfTheseus, Athenian hero and king]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeRoleOfTheseus Context triple: [Theseus and the Amazons, narrativeRoleOfTheseus, Athenian hero and king]
-
A.
combatOutcomeWithTheseus
Indicates the result or consequence of a combat encounter involving Theseus and another entity.
-
B.
relationshipToHermia
Indicates the specific type of personal or social relationship that one entity has with Hermia.
-
C.
roleInHecuba
Indicates that an entity has a specific role or character assignment in the play *Hecuba*.
-
D.
roleInRomeoAndJuliet
Indicates the specific character or part that an entity plays in the work "Romeo and Juliet."
-
E.
goalInTrojanWar
Indicates that an entity’s objective, aim, or purpose is specifically directed toward or realized within the context of the Trojan War.
- F. None of above. chosen
Provenance (4 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_69e288c184b081909f1f1751fb8e299a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1da52b9d48190b503fad5ff70e4c6 |
completed | April 29, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 10:36 p.m.