Triple
T5479452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSPF |
E123434
|
entity |
| Predicate | IPv6Variant |
P2546
|
FINISHED |
| Object | OSPFv3 |
—
|
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: OSPFv3 | Statement: [OSPF, IPv6Variant, OSPFv3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IPv6Variant Context triple: [OSPF, IPv6Variant, OSPFv3]
-
A.
addressFamily
chosen
Indicates the type of network address family (such as IPv4 or IPv6) associated with or used by an entity in a communication context.
-
B.
upperStageVariant
Indicates that one upper stage is a specific version or configuration variant of another upper stage within a launch vehicle system.
-
C.
usesAnycast
Indicates that an entity routes or delivers its services using anycast, where the same IP address is advertised from multiple locations and traffic is directed to the nearest or best-performing instance.
-
D.
protocolFamily
Indicates that one protocol belongs to, or is categorized under, a broader protocol family or group.
-
E.
supportsVLANTagging
Indicates that one entity provides the capability for another entity or interface to handle and process VLAN-tagged network traffic.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9247a16c8190ac5a02534da48853 |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.