Triple
T29079542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donna Troy |
E733933
|
entity |
| Predicate | familyRelationTypeWithHippolyta |
P176003
|
FINISHED |
| Object | adoptive daughter |
—
|
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: adoptive daughter | Statement: [Donna Troy, familyRelationTypeWithHippolyta, adoptive daughter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyRelationTypeWithHippolyta Context triple: [Donna Troy, familyRelationTypeWithHippolyta, adoptive daughter]
-
A.
relationshipToHeracles
Indicates the specific familial or social relationship that an entity has to Heracles.
-
B.
relationshipToHermia
Indicates the specific type of personal or social relationship that one entity has with Hermia.
-
C.
relationshipToPriamAndHecuba
Indicates a familial or relational connection that an entity has specifically to both Priam and Hecuba.
-
D.
familyRelationTypeWithDianaPrince
Indicates the specific type of familial relationship an entity has with Diana Prince.
-
E.
relationshipToDeianira
Indicates a specified type of relationship that one entity has to Deianira, such as familial, romantic, or social connection.
- 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6db3606808190a80c6e9f5da5b33e |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db1bc348819097c844f76e2fa4fe |
completed | May 3, 2026, 5:20 a.m. |
Created at: April 28, 2026, 10:53 a.m.