Triple
T27730277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAPI over HTTP |
E697413
|
entity |
| Predicate | replacesProtocol |
P79404
|
FINISHED |
| Object | RPC over HTTP |
—
|
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: RPC over HTTP | Statement: [MAPI over HTTP, replacesProtocol, RPC over HTTP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesProtocol Context triple: [MAPI over HTTP, replacesProtocol, RPC over HTTP]
-
A.
canOverrideProtocol
Indicates that one entity has the authority or capability to bypass, supersede, or modify an established protocol governing another entity or process.
-
B.
specifiesProtocol
Indicates that one entity defines or designates the communication or interaction protocol to be used by another entity.
-
C.
targetProtocol
Indicates the communication protocol that an action, message, or connection is intended to use or be directed toward.
-
D.
updateProtocol
chosen
Indicates that an entity modifies or revises an existing protocol, procedure, or set of rules to a newer or improved version.
-
E.
updatesProtocolBehaviorOf
Indicates that one entity modifies or changes the protocol behavior or operational rules of another entity.
- 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_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 27, 2026, 3:11 p.m.