Triple
T2529913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pontiac Fiero |
E56131
|
entity |
| Predicate | safetyRecall |
P39398
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Pontiac Fiero, safetyRecall, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyRecall Context triple: [Pontiac Fiero, safetyRecall, yes]
-
A.
recalledIn
Indicates that an entity is mentioned, remembered, or brought up again within a specific context, such as a document, conversation, or event.
-
B.
safetyRelevant
Indicates that the associated entity, condition, or information has a direct impact on safety or is critical for preventing harm or accidents.
-
C.
notableSafety
Indicates that an entity is recognized for having significant safety characteristics, performance, or impact relative to others.
-
D.
safetyLabel
Indicates that an entity has been assigned a safety-related classification or warning status.
-
E.
safety
Indicates that an entity provides, ensures, or is associated with protection from harm, danger, or risk for another entity or within a given context.
- 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_69ab4a48e4f081908f1218d244608659 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd276930c8190bd46b52e06b7098e |
completed | March 7, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69abd0c2e34c8190a914d5c2afba147c |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd18e72a88190bdcf12b326d42fad |
completed | March 7, 2026, 7:19 a.m. |
Created at: March 6, 2026, 9:46 p.m.