Triple
T36624746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IETF |
E904139
|
entity |
| Predicate | standardsTrackIncludes |
P5497
|
FINISHED |
| Object | Proposed Standard |
—
|
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: Proposed Standard | Statement: [IETF, standardsTrackIncludes, Proposed Standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardsTrackIncludes Context triple: [IETF, standardsTrackIncludes, Proposed Standard]
-
A.
includesStandard
Indicates that one entity contains, incorporates, or makes use of a particular standard as part of its definition, implementation, or specification.
-
B.
onStandardsTrack
chosen
Indicates that the subject is part of an officially recognized, actively developed standards process or pathway toward becoming a formal standard.
-
C.
isPartOfStandard
Indicates that something belongs to, is included within, or conforms to a defined standard or standardized set.
-
D.
isPopularStandardFor
Indicates that something is widely accepted and commonly used as the standard choice for a particular purpose or context.
-
E.
isStandardOf
Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 3, 2026, 4:11 p.m.