Triple
T2178486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7143 |
E48585
|
entity |
| Predicate | standardsTrackLevel |
P8040
|
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: [RFC 7143, standardsTrackLevel, Proposed Standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardsTrackLevel Context triple: [RFC 7143, standardsTrackLevel, Proposed Standard]
-
A.
onStandardsTrack
Indicates that the subject is part of an officially recognized, actively developed standards process or pathway toward becoming a formal standard.
-
B.
standardizationStatus
chosen
Indicates the current stage or condition of an entity in a formal standardization process (e.g., proposed, under review, approved, deprecated).
-
C.
firstStandardApproved
Indicates that an entity is the earliest or initial standard that has received formal approval.
-
D.
documentationLevel
Indicates the extent or thoroughness to which something is described, specified, or supported by written or recorded documentation.
-
E.
standardizationScope
Indicates the extent or domain within which a standard or standardization effort is intended to apply or be enforced.
- 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_69a88aa3faa48190995b233af6525815 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc4358fc88190a6f556c2de9fef8c |
completed | March 7, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69abbda0ec948190be88c1243d81a423 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.