Triple
T4513694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AP |
E102106
|
entity |
| Predicate | precedesInPlateNumber |
P51042
|
FINISHED |
| Object | regional transport office code |
—
|
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: regional transport office code | Statement: [AP, precedesInPlateNumber, regional transport office code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precedesInPlateNumber Context triple: [AP, precedesInPlateNumber, regional transport office code]
-
A.
isOnLicensePlateBeforeNumber
chosen
Indicates that one element appears on a license plate in a position preceding a specified number.
-
B.
precedesNumeral
Indicates that one numeral comes before another numeral in a specified ordering or sequence.
-
C.
precedesLetter
Indicates that one letter comes immediately before another letter in a specified ordering, such as the alphabet or a given sequence.
-
D.
plateNumberOf
Indicates the license plate number that is assigned to or associated with a particular vehicle.
-
E.
firstCharactersOfPlate
Indicates that one entity specifies the initial characters appearing at the beginning of another entity’s license plate identifier.
- 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd572402f481908151f7899bc96306 |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd521abea48190b3e758a1f98dd55e |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:02 p.m.