Triple
T1081786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IS-IS for IPv6 |
E23961
|
entity |
| Predicate | usesProtocolNumber |
P3682
|
FINISHED |
| Object | ISO 10589 (CLNS over Layer 2) |
—
|
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: ISO 10589 (CLNS over Layer 2) | Statement: [IS-IS for IPv6, usesProtocolNumber, ISO 10589 (CLNS over Layer 2)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesProtocolNumber Context triple: [IS-IS for IPv6, usesProtocolNumber, ISO 10589 (CLNS over Layer 2)]
-
A.
protocolNumber
chosen
Indicates the specific identifying number assigned to a protocol that governs or documents an interaction, process, or agreement between entities.
-
B.
usesProtocolSuite
Indicates that one entity operates or communicates by employing the set of communication protocols defined by another entity’s protocol suite.
-
C.
hasProtocol
Indicates that an entity uses, follows, or is governed by a specified protocol or set of procedural rules.
-
D.
specifiesProtocol
Indicates that one entity defines or designates the communication or interaction protocol to be used by another entity.
-
E.
protocolNumberSpace
Indicates that there is a defined set or range of valid protocol numbers associated with the given protocol or system.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b95d35888190a20593a278175df7 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73f4310819086281f8ec67d1a32 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.