Triple
T20005909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Child of Deaf Adults |
E494460
|
entity |
| Predicate | hasParentCharacteristic |
P274
|
FINISHED |
| Object | deaf parent |
—
|
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: deaf parent | Statement: [Child of Deaf Adults, hasParentCharacteristic, deaf parent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentCharacteristic Context triple: [Child of Deaf Adults, hasParentCharacteristic, deaf parent]
-
A.
hasParentCharacter
Indicates that one character is the parent of another character.
-
B.
hasCharacteristic
chosen
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
-
C.
hasParentSystem
Indicates that one system is hierarchically contained within or derived from another, which serves as its parent system.
-
D.
hasParentCartridge
Indicates that one cartridge is derived from, contained within, or otherwise hierarchically related as a child to another cartridge designated as its parent.
-
E.
hasParentUnit
Indicates that one unit is hierarchically contained within or belongs to another, higher-level unit.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a57ef881909115c8aa232b1012 |
completed | April 20, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:33 p.m.