Triple
T8470893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Routing Table Maintenance Protocol |
E200276
|
entity |
| Predicate | updateStrategy |
P6360
|
FINISHED |
| Object | periodic updates |
—
|
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: periodic updates | Statement: [Routing Table Maintenance Protocol, updateStrategy, periodic updates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updateStrategy Context triple: [Routing Table Maintenance Protocol, updateStrategy, periodic updates]
-
A.
updatesSpecificationOf
Indicates that one entity revises, modifies, or replaces the existing specification of another entity.
-
B.
updateProtocol
Indicates that an entity modifies or revises an existing protocol, procedure, or set of rules to a newer or improved version.
-
C.
updated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
-
D.
updateSource
Indicates that one entity serves as the origin or provider of information, data, or content used to modify or refresh another entity.
-
E.
updateProcess
chosen
Indicates the action or procedure by which an existing item, system, or state is modified to a newer or revised version.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f234c481909534de6fd702f4cf |
completed | March 31, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.