Triple
T20927635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standardization Administration of China |
E515386
|
entity |
| Predicate | standardTypeManaged |
P141716
|
FINISHED |
| Object | GB standards |
—
|
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: GB standards | Statement: [Standardization Administration of China, standardTypeManaged, GB standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardTypeManaged Context triple: [Standardization Administration of China, standardTypeManaged, GB standards]
-
A.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
B.
standardMaintained
Indicates that a specified standard is being upheld, preserved, or kept in compliance over time within the relevant context.
-
C.
standardCreated
Indicates that an entity is responsible for the creation or establishment of a particular standard.
-
D.
standardMaintainedBy
Indicates that a particular standard is maintained, managed, or overseen by a specified entity.
-
E.
standardsType
Indicates the classification or category of standards that apply to or are associated with an entity or activity.
- F. None of above. chosen
Provenance (4 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_69e0b4fb431c8190b9d40e6a72f0cc87 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f652c3188190ace50415b3b30b83 |
completed | April 21, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53d22d08190bc17ed4bed53804a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:49 p.m.