Triple
T18856728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samantha Cole |
E461189
|
entity |
| Predicate | hasChildrenInStory |
P82383
|
FINISHED |
| Object | two children |
—
|
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: two children | Statement: [Samantha Cole, hasChildrenInStory, two children]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChildrenInStory Context triple: [Samantha Cole, hasChildrenInStory, two children]
-
A.
hasSiblingInStory
Indicates that one character in a narrative has at least one sibling who also appears within the same story.
-
B.
hasChildInFiction
chosen
Indicates that a fictional work or character includes another character as their child within the fictional narrative.
-
C.
childInStory
Indicates that one entity is a child character who appears within the narrative context of the other entity (a story).
-
D.
hasVariantStoriesIn
Indicates that an entity has alternative or differing narrative versions that occur or are found within a specified context or source.
-
E.
hasAllyInStory
Indicates that one entity is portrayed as an ally or supportive partner of another entity within the context of a specific story or narrative.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c05d0bb8819094d0447441f85b57 |
completed | April 20, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.