Triple
T38123774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Accidents |
E952010
|
entity |
| Predicate | involvesMissingChildPlot |
P198409
|
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: [Little Accidents, involvesMissingChildPlot, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesMissingChildPlot Context triple: [Little Accidents, involvesMissingChildPlot, true]
-
A.
depictsChild
Indicates that one entity visually represents or portrays another entity in the role or state of being a child.
-
B.
missingOrgan
Indicates that an entity lacks or no longer possesses a specific organ that would normally be present.
-
C.
wentMissingOn
Indicates that an entity disappeared or became unaccounted for starting on a specific date or time.
-
D.
childRepresents
Indicates that a child entity serves as a representation, proxy, or stand-in for another entity in some context or structure.
-
E.
illegitimateChildOf
Indicates that one person is the child of another, but the parent–child relationship is not recognized as lawful or legitimate under the relevant social or legal norms.
- 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_69f76f07734c8190814e937e12257a78 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fee0b2da3c8190a3519d0564f2f32d |
completed | May 9, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69fee05b315c819081dfcbfb15273487 |
completed | May 9, 2026, 7:20 a.m. |
| PDg | Predicate description generation | batch_69fee0b03a0c81909117dc5915d77295 |
completed | May 9, 2026, 7:22 a.m. |
Created at: May 3, 2026, 4:21 p.m.