Triple
T9313125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F-root |
E224051
|
entity |
| Predicate | usesRoutingTechnique |
P64008
|
FINISHED |
| Object | BGP anycast |
—
|
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: BGP anycast | Statement: [F-root, usesRoutingTechnique, BGP anycast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRoutingTechnique Context triple: [F-root, usesRoutingTechnique, BGP anycast]
-
A.
usesRoutingType
chosen
Indicates that one entity employs or operates according to a specific routing type or routing method associated with another entity.
-
B.
supportsRouting
Indicates that one entity provides the capability to determine and direct paths or routes for another entity’s traffic, requests, or messages.
-
C.
usedRoutes
Indicates that an entity has utilized or traveled along specific routes.
-
D.
routingCapability
Indicates the ability of an entity to determine and direct the path that data, messages, or items should take through a network or system.
-
E.
allowedTechnique
Indicates that a particular technique or method is permitted or acceptable to use in a given context or under specified rules.
- 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20b048a081909fd7ec0b6b863063 |
completed | April 1, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:37 p.m.