Triple
T17903959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keivonn Montreal Woodard |
E447651
|
entity |
| Predicate | usesCommunicationMode |
P112150
|
FINISHED |
| Object | sign language |
—
|
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: sign language | Statement: [Keivonn Montreal Woodard, usesCommunicationMode, sign language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCommunicationMode Context triple: [Keivonn Montreal Woodard, usesCommunicationMode, sign language]
-
A.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
B.
usedToCommunicate
Indicates that one entity serves as a medium or tool through which another entity conveys information, messages, or signals.
-
C.
communicationCapability
Indicates that one entity has the ability or means to communicate with another entity through some channel or modality.
-
D.
designedToCommunicate
Indicates that something has been intentionally created or configured for the purpose of conveying information or messages to others.
-
E.
hasCommunicationType
chosen
Indicates that one entity uses, supports, or is associated with a particular form or mode of communication.
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49e9a9cfc8190879fc36dfdeb562b |
completed | April 19, 2026, 9:21 a.m. |
| PD | Predicate disambiguation | batch_69e3d8ec2f6881909d7f54b878cbed37 |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:19 a.m.