Triple
T1956636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SA |
E42283
|
entity |
| Predicate | usedInVehicleRegistrationCode |
P6238
|
FINISHED |
| Object | SA |
—
|
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: SA | Statement: [SA, usedInVehicleRegistrationCode, SA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInVehicleRegistrationCode Context triple: [SA, usedInVehicleRegistrationCode, SA]
-
A.
vehicleRegistrationCode
Indicates the official registration identifier assigned to a vehicle, typically used for legal identification and record-keeping.
-
B.
vehicleUsed
Indicates that a particular vehicle is utilized or employed in performing an action, event, or activity.
-
C.
designationUsedFor
chosen
Indicates that a particular name, label, or title is employed to refer to or identify a specific entity or role.
-
D.
appliedToVehicleType
Indicates that something (such as a rule, restriction, or condition) is specifically applicable to a particular type or category of 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_69a8870eea088190a38781990812a9bc |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb68a8e608190bc37a85913b3cd44 |
completed | March 7, 2026, 5:24 a.m. |
| PD | Predicate disambiguation | batch_69abaff5dbd48190a9d36ca60de151db |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.