Triple
T29547711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X.400 |
E749673
|
entity |
| Predicate | hasUserProtocol |
P9964
|
FINISHED |
| Object | P2 protocol |
—
|
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: P2 protocol | Statement: [X.400, hasUserProtocol, P2 protocol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUserProtocol Context triple: [X.400, hasUserProtocol, P2 protocol]
-
A.
hasProtocol
chosen
Indicates that an entity uses, follows, or is governed by a specified protocol or set of procedural rules.
-
B.
hasProtocolRole
Indicates that an entity participates in a protocol by fulfilling a specific role or function within that protocol.
-
C.
hasFlagProtocol
Indicates that an entity is associated with, governed by, or operates under a specific flag protocol or set of flag-related rules.
-
D.
hasProtocolStatus
Indicates that an entity is associated with a particular protocol-related state or condition it currently holds.
-
E.
hasUserPort
Indicates that an entity is associated with, exposes, or is accessible through a specific user-facing port or interface.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 5:09 p.m.