Triple
T7858479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NetBEUI |
E182434
|
entity |
| Predicate | routingCapability |
P79412
|
FINISHED |
| Object | non-routable |
—
|
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: non-routable | Statement: [NetBEUI, routingCapability, non-routable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routingCapability Context triple: [NetBEUI, routingCapability, non-routable]
-
A.
supportsRouting
Indicates that one entity provides the capability to determine and direct paths or routes for another entity’s traffic, requests, or messages.
-
B.
routeNetworkType
Indicates the specific kind of transportation or communication network to which a route belongs (e.g., road, rail, or air).
-
C.
routeNetworkCharacteristic
Indicates a relationship where a specific characteristic or property is attributed to a route within a network.
-
D.
routingProtocol
Indicates that one entity uses, implements, or is associated with a specific routing protocol to determine paths for forwarding data in a network.
-
E.
supportsHierarchicalRouting
Indicates that one entity enables or is compatible with routing that uses a multi-level or hierarchical structure of routing domains or paths.
- 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_69ca82887fd48190975896bf38c4596b |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb1a787c8c8190bcd9ed76cc7aa4c5 |
completed | March 31, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69cae925ca388190ae4a01fa76e957e8 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf786ec748190b6347b0c94335550 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:52 p.m.