Triple
T1081789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IS-IS for IPv6 |
E23961
|
entity |
| Predicate | discovers |
P3851
|
FINISHED |
| Object | adjacencies between IS-IS routers |
—
|
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: adjacencies between IS-IS routers | Statement: [IS-IS for IPv6, discovers, adjacencies between IS-IS routers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discovers Context triple: [IS-IS for IPv6, discovers, adjacencies between IS-IS routers]
-
A.
discovery
Indicates the event or process by which one entity finds, uncovers, or identifies something previously unknown or unrecognized.
-
B.
finds
chosen
Indicates that one entity discovers, locates, or comes upon another entity, often as the result of a search or encounter.
-
C.
explores
Indicates actively investigating, traveling through, or examining something in order to discover or learn more about it.
-
D.
coDiscovererOf
Indicates that two or more entities jointly discovered the same object, phenomenon, or finding.
-
E.
discloses
Indicates that one entity reveals, makes known, or provides previously non-public information to another entity or to the public.
- 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.