Triple
T27658135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WG 14 |
E697046
|
entity |
| Predicate | standardNumberManaged |
P4626
|
FINISHED |
| Object | ISO/IEC 9899:1990 |
—
|
NE NERFINISHED |
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: ISO/IEC 9899:1990 | Statement: [WG 14, standardNumberManaged, ISO/IEC 9899:1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardNumberManaged Context triple: [WG 14, standardNumberManaged, ISO/IEC 9899:1990]
-
A.
standardNumber
chosen
Indicates that an entity is associated with a canonical or officially recognized reference number used for identification or classification.
-
B.
standardTypeManaged
Indicates that an entity is governed, controlled, or handled according to a defined standard type or classification.
-
C.
standardNumberStandardizedBy
Indicates that a standard number has been formally defined, approved, or regulated by a specific standardizing authority or organization.
-
D.
standardSetSize
Indicates that there is a defined or typical number of elements that constitute the standard size for a given set.
-
E.
standardMaintained
Indicates that a specified standard is being upheld, preserved, or kept in compliance over time within the relevant context.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 2:35 p.m.