Triple
T27500825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adonis Johnson |
E694145
|
entity |
| Predicate | hasDisabilityInFamily |
P92492
|
FINISHED |
| Object | daughter Amara is deaf |
—
|
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: daughter Amara is deaf | Statement: [Adonis Johnson, hasDisabilityInFamily, daughter Amara is deaf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisabilityInFamily Context triple: [Adonis Johnson, hasDisabilityInFamily, daughter Amara is deaf]
-
A.
hadMemberFamily
Indicates that an entity was a member of a particular family group during a specified time or context.
-
B.
hasFamilySituation
chosen
Indicates the familial status or circumstances that apply to an entity, such as their family composition, responsibilities, or living situation.
-
C.
hasDisabilityRepresentation
Indicates that something includes, portrays, or accounts for the presence and experiences of people with disabilities.
-
D.
hasFamilyRole
Indicates that one entity holds a specific familial role or position in relation to another entity.
-
E.
hasFamilyOrganization
Indicates that an entity is associated with, belongs to, or is structured within a particular family-based organizational unit or system.
- 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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 27, 2026, 1:11 p.m.