Triple
T7817125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DF |
E181037
|
entity |
| Predicate | vehicleRegistrationScope |
P41345
|
FINISHED |
| Object | state-level in Brazil |
—
|
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: state-level in Brazil | Statement: [DF, vehicleRegistrationScope, state-level in Brazil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehicleRegistrationScope Context triple: [DF, vehicleRegistrationScope, state-level in Brazil]
-
A.
identifiesVehiclesRegisteredIn
chosen
Indicates that an entity specifies or determines which vehicles are registered within a particular scope or authority.
-
B.
vehicleRegistrationCode
Indicates the official registration identifier assigned to a vehicle, typically used for legal identification and record-keeping.
-
C.
vehicleRegistrationCategory
Indicates the classification or type of registration assigned to a vehicle under a specific regulatory or administrative scheme.
-
D.
vehiclePolicy
Indicates a relationship where a policy governs, regulates, or defines rules and conditions for the use, operation, or management of a vehicle.
-
E.
vehicleStandard
Indicates that something complies with, or is defined according to, a specified vehicle-related standard or regulatory specification.
- 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_69ca828153f48190bdb27ac46f8e0745 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf96ea6d881908eff5f750e0f6700 |
completed | March 30, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69cae91687788190af9cb7aaa996d291 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:39 p.m.