Triple
T19398111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAE J3016 |
E485244
|
entity |
| Predicate | classificationSchemeType |
P6736
|
FINISHED |
| Object | level-based classification |
—
|
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: level-based classification | Statement: [SAE J3016, classificationSchemeType, level-based classification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classificationSchemeType Context triple: [SAE J3016, classificationSchemeType, level-based classification]
-
A.
classificationSystem
chosen
Indicates a relationship where an entity is organized or categorized according to a particular classification scheme or taxonomy.
-
B.
classificationSystemName
Indicates the name or label assigned to a particular classification system used to categorize or organize entities.
-
C.
designationScheme
Indicates the classification or naming system under which an entity’s designations or identifiers are defined.
-
D.
classificationReference
Indicates that one entity serves as a reference or source for the classification or categorization applied to another entity.
-
E.
classificationSystemBasedOn
Indicates that one classification system is organized, defined, or derived using another classification system as its basis or reference framework.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62574edd08190b5456108d5e3907e |
completed | April 20, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:36 p.m.