Triple
T5101259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CODA |
E114984
|
entity |
| Predicate | protagonistRoleInFamily |
P20969
|
FINISHED |
| Object | child of deaf adults |
—
|
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: child of deaf adults | Statement: [CODA, protagonistRoleInFamily, child of deaf adults]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistRoleInFamily Context triple: [CODA, protagonistRoleInFamily, child of deaf adults]
-
A.
hasFamilyRole
Indicates that one entity holds a specific familial role or position in relation to another entity.
-
B.
protagonistType
chosen
Indicates the role or category that the main character (protagonist) of a story or scenario belongs to.
-
C.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
D.
protagonistDescription
Indicates that a text provides a descriptive summary or characterization of the story’s main protagonist.
-
E.
hasProtagonistRelationship
Indicates that there exists a central, story-driving relationship involving the protagonist and another entity within a 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_69bd4440b3348190be1251fd8b7951f1 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7584ed408190a6d1086588f24faa |
completed | March 20, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69bd715e06808190931934dc9930f997 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:40 p.m.