Triple
T16988191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Automatic Warning System |
E412123
|
entity |
| Predicate | indicatesWarning |
P101040
|
FINISHED |
| Object | horn sound in cab |
—
|
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: horn sound in cab | Statement: [Automatic Warning System, indicatesWarning, horn sound in cab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indicatesWarning Context triple: [Automatic Warning System, indicatesWarning, horn sound in cab]
-
A.
warnsAbout
Indicates that one entity alerts or cautions another entity about a potential danger, risk, or problem.
-
B.
warningIssued
Indicates that a formal warning or alert has been communicated from one entity to another regarding a potential or existing risk, problem, or violation.
-
C.
warningGivenBy
Indicates that one entity issues or delivers a warning to another entity.
-
D.
warningIncludes
chosen
Indicates that a warning message or notice contains or encompasses specific information, elements, or details.
-
E.
warningType
Indicates the specific category or classification of a warning associated with an entity or event.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d27cd2048190800a60ae653e11e1 |
completed | April 18, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.