Triple
T1649206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BCP 14 |
E35652
|
entity |
| Predicate | standardizesUseOf |
P1371
|
FINISHED |
| Object | "MUST" |
—
|
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: "MUST" | Statement: [BCP 14, standardizesUseOf, "MUST"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardizesUseOf Context triple: [BCP 14, standardizesUseOf, "MUST"]
-
A.
usesStandard
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
-
B.
standardizedIn
Indicates that something has been formally defined, regulated, or made uniform within a particular standard, framework, or jurisdiction.
-
C.
standardizedFor
Indicates that something has been adjusted or converted to conform to a common standard, format, or reference so it can be consistently compared or used.
-
D.
standardizationApproach
Indicates the method or strategy used to establish, implement, or align with a common standard across entities or processes.
-
E.
standardizedBy
chosen
Indicates that one entity defines, regulates, or formalizes the standards or specifications by which another entity is created, measured, or operated.
- 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_69a8860568888190a32cd9f70acbba42 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaa0fbe984819084f8daee81ca9b67 |
completed | March 6, 2026, 9:40 a.m. |
| PD | Predicate disambiguation | batch_69a907ce4dd881909168a1e99505d4ec |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:29 p.m.