Triple
T21091639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RIP |
E519651
|
entity |
| Predicate | usesRoutePoisoning |
P142811
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [RIP, usesRoutePoisoning, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRoutePoisoning Context triple: [RIP, usesRoutePoisoning, yes]
-
A.
usesNeighborDiscovery
Indicates that an entity employs a neighbor discovery mechanism to detect, identify, or maintain information about adjacent or nearby entities in a network or environment.
-
B.
avoidsRoute
Indicates that an entity deliberately does not use or travel along a particular route.
-
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.
usesRoutingType
Indicates that one entity employs or operates according to a specific routing type or routing method associated with another entity.
-
E.
usedRoutes
Indicates that an entity has utilized or traveled along specific routes.
- F. None of above. chosen
Provenance (4 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7094f6ebc8190a90b014755a9d4a6 |
completed | April 21, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2e03d88819086f8b641656ad8b0 |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 2:51 p.m.