Triple
T14512950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GSO |
E340442
|
entity |
| Predicate | standardScope |
P19702
|
FINISHED |
| Object | industrial products |
—
|
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: industrial products | Statement: [GSO, standardScope, industrial products]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardScope Context triple: [GSO, standardScope, industrial products]
-
A.
typicalScope
Indicates the usual or expected range, extent, or domain within which something normally applies, operates, or is relevant.
-
B.
standardizationScope
chosen
Indicates the extent or domain within which a standard or standardization effort is intended to apply or be enforced.
-
C.
scopeDefault
Indicates that something applies or is valid in the absence of a more specific or overriding scope.
-
D.
standardWithin
Indicates that one entity conforms to, or falls within the limits of, a specified standard defined by another entity.
-
E.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de9a6c6054819086b4c0ce1d83fdc5 |
completed | April 14, 2026, 7:50 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:21 a.m.