Triple
T38131301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIA Grade 6 |
E952227
|
entity |
| Predicate | safetyClassificationLevel |
P7279
|
FINISHED |
| Object | entry-level |
—
|
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: entry-level | Statement: [FIA Grade 6, safetyClassificationLevel, entry-level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyClassificationLevel Context triple: [FIA Grade 6, safetyClassificationLevel, entry-level]
-
A.
classificationLevel
chosen
Indicates the degree or tier within an ordered system or hierarchy to which something is assigned for categorization or control purposes.
-
B.
securityClassification
Indicates the level or category of security sensitivity or access restriction assigned to an entity.
-
C.
safetyCategory
Indicates the classification of something according to its level or type of safety.
-
D.
safetyRatingHighlight
Indicates that an entity’s safety rating is emphasized or specially marked as noteworthy compared to others.
-
E.
hazardLevelSystem
Indicates a system’s assigned degree of risk or danger within a defined hazard classification 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:21 p.m.