Triple
T13651671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BCP 39 |
E326753
|
entity |
| Predicate | typeOfStandardizationDocument |
P43031
|
FINISHED |
| Object | process and organizational guideline |
—
|
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: process and organizational guideline | Statement: [BCP 39, typeOfStandardizationDocument, process and organizational guideline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfStandardizationDocument Context triple: [BCP 39, typeOfStandardizationDocument, process and organizational guideline]
-
A.
standardsType
chosen
Indicates the classification or category of standards that apply to or are associated with an entity or activity.
-
B.
standardizationStatus
Indicates the current stage or condition of an entity in a formal standardization process (e.g., proposed, under review, approved, deprecated).
-
C.
legalStandardType
Indicates the specific type or category of legal standard that governs or applies to a given legal rule, decision, or evaluation.
-
D.
isStandardOf
Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
-
E.
documentationStandard
Indicates that there is a specified convention or set of rules governing how documentation should be written, structured, or maintained in relation to an entity or process.
- 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc609676c8190b5b1cabe6b315142 |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:52 p.m.