Triple
T21226803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Service Communication Proxy |
E523103
|
entity |
| Predicate | handlesCommunicationType |
P112150
|
FINISHED |
| Object | service-based interfaces |
—
|
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: service-based interfaces | Statement: [Service Communication Proxy, handlesCommunicationType, service-based interfaces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesCommunicationType Context triple: [Service Communication Proxy, handlesCommunicationType, service-based interfaces]
-
A.
hasCommunicationType
chosen
Indicates that one entity uses, supports, or is associated with a particular form or mode of communication.
-
B.
hasCommunicationCodeType
Indicates that an entity is associated with a specific type or category of communication code (e.g., phone, fax, email, messaging).
-
C.
hasCommunicationClass
Indicates that one entity is assigned to, or associated with, a particular category or class of communication.
-
D.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
E.
handlesOperationType
Indicates that an entity is responsible for processing or managing a specific type or category of operation.
- 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734ac42a08190b95a24acf5f0779b |
completed | April 21, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:44 p.m.