Triple
T12298807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Road Safety Corps |
E293161
|
entity |
| Predicate | usesMarkedVehicles |
P104330
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Federal Road Safety Corps, usesMarkedVehicles, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMarkedVehicles Context triple: [Federal Road Safety Corps, usesMarkedVehicles, true]
-
A.
usedPoliticalVehicle
Indicates that an entity employed a political organization, campaign, or platform as a means or instrument to achieve its goals or carry out actions.
-
B.
usesArmoredVehicle
Indicates that an entity employs or operates an armored vehicle in performing an action or fulfilling a role.
-
C.
usedMark
Indicates that one entity has employed or applied a particular mark, symbol, or indicator in some context or action.
-
D.
usedOnOfficialPlatesIn
Indicates that something is employed or displayed on official license plates within a specified jurisdiction or region.
-
E.
identifiesVehiclesRegisteredIn
Indicates that an entity specifies or determines which vehicles are registered within a particular scope or authority.
- 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_69d6ab690ad081908c0ed3870ec82d53 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec02c008190a56aae60a3d9eff6 |
completed | April 10, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69d93f607a88819089e89fd263ae9937 |
completed | April 10, 2026, 6:20 p.m. |
Created at: April 8, 2026, 9:52 p.m.