Triple
T27730303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAPI over HTTP |
E697413
|
entity |
| Predicate | defaultProtocolSince |
P107773
|
FINISHED |
| Object | Exchange Server 2016 |
—
|
NE NERFINISHED |
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: Exchange Server 2016 | Statement: [MAPI over HTTP, defaultProtocolSince, Exchange Server 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultProtocolSince Context triple: [MAPI over HTTP, defaultProtocolSince, Exchange Server 2016]
-
A.
specifiesProtocol
Indicates that one entity defines or designates the communication or interaction protocol to be used by another entity.
-
B.
specifiesProtocolVersion
Indicates that an entity defines or sets the particular protocol version to be used in a communication or interaction.
-
C.
hasProtocol
Indicates that an entity uses, follows, or is governed by a specified protocol or set of procedural rules.
-
D.
defaultBehaviorSinceVersion
Indicates that a particular behavior has been the default starting from a specified version onward.
-
E.
primaryProtocol
chosen
Indicates that one protocol is designated as the main or default protocol used in a given context or interaction.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 3:11 p.m.