Triple
T32378743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Model-View-Presenter |
E827354
|
entity |
| Predicate | typicalCommunication |
P107806
|
FINISHED |
| Object | view communicates with presenter |
—
|
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: view communicates with presenter | Statement: [Model-View-Presenter, typicalCommunication, view communicates with presenter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCommunication Context triple: [Model-View-Presenter, typicalCommunication, view communicates with presenter]
-
A.
communicationTrait
Indicates a characteristic or quality related to how an entity communicates or engages in communication.
-
B.
typicalInteraction
chosen
Indicates the usual or most common way in which two entities interact or relate to each other.
-
C.
communicationsStandard
Indicates that there is a specified communications protocol or standard governing how information is transmitted or exchanged between the related entities.
-
D.
communicationPrinciple
Indicates a guiding rule or norm that shapes how communication should be conducted between entities.
-
E.
typicalSpeaker
Indicates that the subject is a prototypical or characteristic speaker or source of utterances in the context of the object.
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:51 a.m.