Triple
T13573000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Creusa |
E324210
|
entity |
| Predicate | abandonedChild |
P28740
|
FINISHED |
| Object | Ion (as an infant) |
—
|
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: Ion (as an infant) | Statement: [Creusa, abandonedChild, Ion (as an infant)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abandonedChild Context triple: [Creusa, abandonedChild, Ion (as an infant)]
-
A.
abandonedIn
Indicates that one entity was left behind or deserted in the location or context specified by another entity.
-
B.
abandonedBy
chosen
Indicates that one entity has been deserted, forsaken, or left behind by another entity that was previously present, responsible, or involved.
-
C.
adoptiveChild
Indicates that one entity is the child of another through legal adoption rather than biological descent.
-
D.
featuresChildAbduction
Indicates that an event, situation, or narrative involves the abduction or kidnapping of a child as a central or notable element.
-
E.
fosterChild
Indicates a relationship where one person is the child being cared for and raised by foster parents who are not their biological or legal parents.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb0106cb48190b20eb9bda131a68a |
completed | April 12, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.