Triple
T23591193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuno |
E582480
|
entity |
| Predicate | communicatesPrimarilyBy |
P3332
|
FINISHED |
| Object | Machine-mediated communication system |
—
|
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: Machine-mediated communication system | Statement: [Kuno, communicatesPrimarilyBy, Machine-mediated communication system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicatesPrimarilyBy Context triple: [Kuno, communicatesPrimarilyBy, Machine-mediated communication system]
-
A.
usedToCommunicate
Indicates that one entity serves as a medium or tool through which another entity conveys information, messages, or signals.
-
B.
communicationTrait
Indicates a characteristic or quality related to how an entity communicates or engages in communication.
-
C.
communicationMode
chosen
Indicates the method or channel through which communication between entities is carried out.
-
D.
designedToCommunicate
Indicates that something has been intentionally created or configured for the purpose of conveying information or messages to others.
-
E.
communicatedAs
Indicates that one entity is expressed, conveyed, or presented in the form, manner, or role of another.
- 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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b035a5d88190bd2e1fa0170045cd |
completed | April 29, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:42 p.m.