Triple
T8918723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet Routing Registry |
E212356
|
entity |
| Predicate | dataConsumer |
P68023
|
FINISHED |
| Object | network route servers |
—
|
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: network route servers | Statement: [Internet Routing Registry, dataConsumer, network route servers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataConsumer Context triple: [Internet Routing Registry, dataConsumer, network route servers]
-
A.
consumes
Indicates that one entity eats, drinks, or otherwise uses up another entity as a resource or nourishment.
-
B.
dataPortal
Indicates that an entity serves as or is associated with an online interface or gateway through which data can be accessed, managed, or distributed.
-
C.
dataAcquisition
chosen
Indicates the process by which one entity obtains, collects, or retrieves data from another source or system.
-
D.
dataControl
Indicates that one entity has the authority or capability to determine how another entity’s data is collected, used, shared, or managed.
-
E.
isConsumerOriented
Indicates that something is designed, targeted, or tailored primarily to meet the needs, preferences, or interests of consumers.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6613639881909090d060f388a865 |
completed | April 1, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:56 p.m.