Triple
T21886560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Signum |
E540419
|
entity |
| Predicate | onboardFunction |
P36407
|
FINISHED |
| Object | automatic emergency brake application |
—
|
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: automatic emergency brake application | Statement: [Signum, onboardFunction, automatic emergency brake application]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onboardFunction Context triple: [Signum, onboardFunction, automatic emergency brake application]
-
A.
onBoard
Indicates that one entity is physically located on or within a vehicle, vessel, or platform operated or used by another entity.
-
B.
onboardPlatform
Indicates that an entity is being added, integrated, or enrolled onto a particular platform so it can start operating or participating there.
-
C.
onBoardService
Indicates that a service is provided to or available for passengers while they are physically on board a vehicle, vessel, or aircraft.
-
D.
onboardLocation
Indicates that one entity is located on or within a vehicle, vessel, or other conveyance associated with another entity.
-
E.
hasOnboardFeature
chosen
Indicates that an entity includes or is equipped with a particular feature as part of its built-in or onboard capabilities.
- 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_69e0c479a98081908ce333853fdd4348 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118ed35948190bbffba2c40029eee |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:05 p.m.