Triple
T33692657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BCP 190 |
E863223
|
entity |
| Predicate | typeOfStandardizationLevel |
P65362
|
FINISHED |
| Object | Best Current Practice |
—
|
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: Best Current Practice | Statement: [BCP 190, typeOfStandardizationLevel, Best Current Practice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfStandardizationLevel Context triple: [BCP 190, typeOfStandardizationLevel, Best Current Practice]
-
A.
hasStandardizationLevel
chosen
Indicates the degree or extent to which something conforms to an established standard or set of standardized criteria.
-
B.
typeOfStandardizationActivity
Indicates the specific kind or category of standardization activity that is being carried out or referenced.
-
C.
standardizationStatus
Indicates the current stage or condition of an entity in a formal standardization process (e.g., proposed, under review, approved, deprecated).
-
D.
isPartOfStandardizationSystem
Indicates that something belongs to, or is included within, a defined standardization framework, scheme, or system.
-
E.
safetyStandardLevel
Indicates the degree or tier of safety requirements or protections that apply to an entity or activity.
- 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00c8e617548190bba4cdfbb6f512e0 |
completed | May 10, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_6a00c7e816b88190bd40f5ea2a768c8b |
completed | May 10, 2026, 6:01 p.m. |
Created at: May 1, 2026, 1:43 a.m.