Triple
T7427770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EIGRP |
E171411
|
entity |
| Predicate | usesMetricComponents |
P49748
|
FINISHED |
| Object | bandwidth |
—
|
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: bandwidth | Statement: [EIGRP, usesMetricComponents, bandwidth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMetricComponents Context triple: [EIGRP, usesMetricComponents, bandwidth]
-
A.
usesMetric
Indicates that one entity adopts, applies, or relies on a particular metric or measurement standard in its operation, evaluation, or description.
-
B.
isMetric
Indicates that something satisfies the properties required to be considered a metric, such as defining distances that obey non-negativity, identity, symmetry, and the triangle inequality.
-
C.
usesMetricSignature
Indicates that one entity adopts or applies a metric signature (a specific pattern of metric signs) defined or provided by another entity.
-
D.
metricComponent
chosen
Indicates a relationship where one element functions as a component or constituent part of a larger metric.
-
E.
usesMeasurementSystem
Indicates that one entity adopts or applies a particular system of measurement defined by another entity.
- 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_69c68a63491881909281f73d4d5643bf |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f306bfe481909f99f6792de95ffc |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f03648d08190b862d07fef71210c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:12 p.m.