Triple
T9818140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1655 |
E238459
|
entity |
| Predicate | definesMetric |
P90167
|
FINISHED |
| Object | etherStatsDropEvents |
—
|
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: etherStatsDropEvents | Statement: [RFC 1655, definesMetric, etherStatsDropEvents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesMetric Context triple: [RFC 1655, definesMetric, etherStatsDropEvents]
-
A.
metricType
Indicates the specific category or kind of measurement that a given metric represents.
-
B.
metricComponent
Indicates a relationship where one element functions as a component or constituent part of a larger metric.
-
C.
metricForm
Indicates that one entity is expressed or represented in a particular metric form or measurement format relative to another.
-
D.
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.
-
E.
metricDependsOn
Indicates that the value or definition of one metric is determined by, derived from, or otherwise reliant on another metric.
- 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_69ca84dfde1481909f47c286d715f892 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb2f5bfa481908a2d2cb3f3d7d585 |
completed | April 2, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cd03e01ea881909a7d93fc3994ace5 |
completed | April 1, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_69cd06abc9248190a506b64e9c516d03 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:31 p.m.