Triple
T9400744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AC |
E226460
|
entity |
| Predicate | countryCodeOnPlate |
P62402
|
FINISHED |
| Object | D |
—
|
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: D | Statement: [AC, countryCodeOnPlate, D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryCodeOnPlate Context triple: [AC, countryCodeOnPlate, D]
-
A.
licensePlateOrigin
Indicates that a vehicle’s license plate was issued or originates from a particular jurisdiction or region.
-
B.
registrationPlateFormat
Indicates the specific pattern or structure that a vehicle’s registration plate must follow (such as the arrangement of letters, numbers, and symbols).
-
C.
countryCodePart
Indicates that one entity is a segment or component of a standardized country code associated with another entity.
-
D.
hasCountyNumberPlateCode
Indicates that an entity (such as a vehicle or registration) bears a number plate code that corresponds to a specific county.
-
E.
usesCodeOnPlates
chosen
Indicates that an entity applies or employs a specific code or coding system on plates.
- 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd5157d66c819094c18f680c7093f7 |
completed | April 1, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69cca545b2448190a4297312e39c21ac |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:46 p.m.