Triple
T7186902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2467 |
E167594
|
entity |
| Predicate | relatedToProtocolVersion |
P75898
|
FINISHED |
| Object | IPv6 |
—
|
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: IPv6 | Statement: [RFC 2467, relatedToProtocolVersion, IPv6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToProtocolVersion Context triple: [RFC 2467, relatedToProtocolVersion, IPv6]
-
A.
protocolVersion
Indicates the specific version of a protocol that governs how two or more entities communicate or interact.
-
B.
associatedProtocol
Indicates that one entity is linked to, governed by, or operates according to a particular protocol.
-
C.
supportedProtocol
Indicates that one entity is compatible with, implements, or can operate using a specified communication or interaction protocol.
-
D.
specifiesProtocolVersion
Indicates that an entity defines or sets the particular protocol version to be used in a communication or interaction.
-
E.
hasProtocol
Indicates that an entity uses, follows, or is governed by a specified protocol or set of procedural rules.
- F. None of above. chosen
Provenance (4 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e9b045c48190b27b2d6f7c11026f |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e74fb0f48190b2ad4dd4efdd241a |
completed | March 27, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69c6e9aeb1b08190ace6f978387c89aa |
completed | March 27, 2026, 8:33 p.m. |
Created at: March 27, 2026, 2:49 p.m.