Triple
T12885852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Singer |
E308222
|
entity |
| Predicate | communicationAbility |
P83331
|
FINISHED |
| Object | 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: deaf | Statement: [John Singer, communicationAbility, deaf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicationAbility Context triple: [John Singer, communicationAbility, deaf]
-
A.
communicationSkill
Indicates the degree to which an entity effectively conveys, receives, and interprets information in interactions with others.
-
B.
communicationTrait
chosen
Indicates a characteristic or quality related to how an entity communicates or engages in communication.
-
C.
communicationCapability
Indicates that one entity has the ability or means to communicate with another entity through some channel or modality.
-
D.
communicationPrinciple
Indicates a guiding rule or norm that shapes how communication should be conducted between entities.
-
E.
communicationFunction
Indicates that one entity serves a communicative role or purpose in relation to another, such as conveying, mediating, or facilitating the exchange of information.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97c7f91d08190aac2f6419d3ba992 |
completed | April 10, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69d96fa55b888190ab1612e93c41aec4 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:39 p.m.