Triple
T1077249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSPFv3 |
E23866
|
entity |
| Predicate | difference |
P3450
|
FINISHED |
| Object | separates protocol from IPv6 addressing |
—
|
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: separates protocol from IPv6 addressing | Statement: [OSPFv3, difference, separates protocol from IPv6 addressing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: difference Context triple: [OSPFv3, difference, separates protocol from IPv6 addressing]
-
A.
distinction
chosen
Indicates that one entity is recognized, treated, or classified as different or separate from another.
-
B.
delta
Indicates a change, difference, or variation between two related quantities, states, or conditions.
-
C.
variant
Indicates that one entity is an alternative form, version, or variation of another entity.
-
D.
disadvantage
Indicates that one entity is in a less favorable, weaker, or hindered position relative to another in a given context.
-
E.
parity
Indicates that two quantities share the same evenness or oddness, or more generally that they have equivalent status or value in a given context.
- 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_69a4b94288d88190aae4fb86236c0702 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73ba8208190be7f3cef8c18689b |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.