Triple
T5486232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GJ-3 |
E123587
|
entity |
| Predicate | registrationPlateFormat |
P64323
|
FINISHED |
| Object | GJ-3 XX 1234 |
—
|
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: GJ-3 XX 1234 | Statement: [GJ-3, registrationPlateFormat, GJ-3 XX 1234]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registrationPlateFormat Context triple: [GJ-3, registrationPlateFormat, GJ-3 XX 1234]
-
A.
isOnLicensePlateBeforeNumber
Indicates that one element appears on a license plate in a position preceding a specified number.
-
B.
licensePlateSystem
Indicates a system or scheme used to assign, format, and manage license plate identifiers for vehicles.
-
C.
firstCharactersOfPlate
Indicates that one entity specifies the initial characters appearing at the beginning of another entity’s license plate identifier.
-
D.
usesCodeOnPlates
Indicates that an entity applies or employs a specific code or coding system on plates.
-
E.
routeNumberFormat
Indicates how the identifying number or code for a route is structured or formatted.
- 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_69bd464a2d908190869324ce176779c8 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd93e5d0f08190a6cc9fc408b7c5bb |
completed | March 20, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69bd91a73b148190a865243536a4fe76 |
completed | March 20, 2026, 6:27 p.m. |
| PDg | Predicate description generation | batch_69bd93e4d2d081908eb75ee22fe72824 |
completed | March 20, 2026, 6:37 p.m. |
Created at: March 20, 2026, 2:10 p.m.