Triple
T18112816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Then She Found Me |
E433521
|
entity |
| Predicate | featuresBirthParentReunion |
P83333
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Then She Found Me, featuresBirthParentReunion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresBirthParentReunion Context triple: [Then She Found Me, featuresBirthParentReunion, true]
-
A.
featuresChildAbduction
Indicates that an event, situation, or narrative involves the abduction or kidnapping of a child as a central or notable element.
-
B.
fosterParents
Indicates a relationship where individuals act as temporary parental caregivers for a child who is not their biological or adopted offspring.
-
C.
fateOfChild
Indicates the outcome or destiny that ultimately befalls a child as a result of certain circumstances, actions, or events.
-
D.
biologicalParent
chosen
Indicates that one entity is the natural (genetic) parent of another entity.
-
E.
parentFormation
Indicates that one geological formation serves as the larger or originating unit from which another formation is derived or classified.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddd3fd9c81909bfe95927f7553e3 |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.