Triple
T5678726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 10589 |
E125148
|
entity |
| Predicate | topologyInformation |
P1372
|
FINISHED |
| Object | Link-state database |
—
|
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: Link-state database | Statement: [ISO 10589, topologyInformation, Link-state database]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topologyInformation Context triple: [ISO 10589, topologyInformation, Link-state database]
-
A.
usesTopology
Indicates that one entity employs, is based on, or operates according to a particular topology defined or provided by another entity.
-
B.
typicalTopology
Indicates the usual or most common network or structural arrangement that characterizes how the related entities are organized or interconnected.
-
C.
hasTopology
Indicates that one entity possesses, exhibits, or is characterized by a particular structural or spatial configuration defined by the other entity.
-
D.
topology
chosen
Indicates the structural or spatial arrangement and connectivity pattern among components within a system.
-
E.
topologyChange
Indicates a change in the structural arrangement or connectivity among components in a system or network.
- 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_69c008295c808190acfe78915e7d656a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c025303860819093e51f176babed71 |
completed | March 22, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69c021bc3894819084f37d14ba4b2644 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.