Triple
T30863514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GB/T charging standard |
E786126
|
entity |
| Predicate | hasSubStandard |
P197131
|
FINISHED |
| Object | GB/T 18487 |
—
|
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/T 18487 | Statement: [GB/T charging standard, hasSubStandard, GB/T 18487]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubStandard Context triple: [GB/T charging standard, hasSubStandard, GB/T 18487]
-
A.
hasSubdivisionStandard
Indicates that a governing standard or specification defines how an entity is to be subdivided into smaller parts or units.
-
B.
hasSubsequentStandard
Indicates that one standard is followed or superseded by another standard that comes after it in sequence or version.
-
C.
hasStandardSubdivisionRange
Indicates that there is a defined range of standard subdivisions applicable to a given entity or classification.
-
D.
isStandardOf
Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
-
E.
hasServiceStandard
Indicates that an entity is associated with, or governed by, a defined service standard specifying expected service levels or quality.
- 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe78e545888190a239af1a84280fa0 |
completed | May 8, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69fe7842742081908043eb950ed69f92 |
completed | May 8, 2026, 11:56 p.m. |
| PDg | Predicate description generation | batch_69fe78e35e6c8190b8b440777912f64e |
completed | May 8, 2026, 11:59 p.m. |
Created at: April 29, 2026, 8:47 p.m.