Triple
T23169607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | black No. 3 Goodwrench Chevrolet |
E578807
|
entity |
| Predicate | safetyEra |
P12725
|
FINISHED |
| Object | pre-HANS device era |
—
|
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: pre-HANS device era | Statement: [black No. 3 Goodwrench Chevrolet, safetyEra, pre-HANS device era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyEra Context triple: [black No. 3 Goodwrench Chevrolet, safetyEra, pre-HANS device era]
-
A.
safetyCategory
Indicates the classification of something according to its level or type of safety.
-
B.
safety
chosen
Indicates that an entity provides, ensures, or is associated with protection from harm, danger, or risk for another entity or within a given context.
-
C.
emissionsEra
Indicates the time period or era during which the emissions associated with an entity occur or are recorded.
-
D.
preservationEra
Indicates the historical or temporal period during which something is preserved, conserved, or maintained.
-
E.
brandEra
Indicates the historical period or era during which a particular brand identity, style, or strategy is in effect.
- 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_69e245fc75348190a0288401044c8af8 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f2f10208190b3a0f9a4c790cb0a |
completed | April 29, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:03 p.m.