Triple
T8984917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dana York |
E214635
|
entity |
| Predicate | hasChildFromPreviousRelationship |
P75214
|
FINISHED |
| Object | one son |
—
|
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: one son | Statement: [Dana York, hasChildFromPreviousRelationship, one son]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChildFromPreviousRelationship Context triple: [Dana York, hasChildFromPreviousRelationship, one son]
-
A.
predecessorRelationship
Indicates that one entity comes before another in an ordered sequence, chain, or lineage, serving as its prior or earlier counterpart.
-
B.
parentRelationship
chosen
Indicates a familial relationship in which one entity is the parent of another entity.
-
C.
hasGenerationRelationship
Indicates that one entity is involved in producing, creating, or giving rise to another entity.
-
D.
isChildOf
Indicates that one entity is the offspring or direct descendant of another entity.
-
E.
hasPredecessorStructureFrom
Indicates that one structure existed or was established before another structure in a sequential or developmental order.
- 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_69ca839f76bc8190a4b7123cdd682199 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc67ecc5188190a6fb4d5456893121 |
completed | April 1, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69cc5edba0f88190b97401636a076d7a |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:03 p.m.