Triple
T4513695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AP |
E102106
|
entity |
| Predicate | followsInPlateNumber |
P51042
|
FINISHED |
| Object | country-wide registration format rules |
—
|
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: country-wide registration format rules | Statement: [AP, followsInPlateNumber, country-wide registration format rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsInPlateNumber Context triple: [AP, followsInPlateNumber, country-wide registration format rules]
-
A.
hasPlate
Indicates that one entity possesses, is equipped with, or includes a plate as part of its attributes or components.
-
B.
isOnLicensePlateBeforeNumber
chosen
Indicates that one element appears on a license plate in a position preceding a specified number.
-
C.
followsRouteOf
Indicates that one entity travels along the same path or route that another entity takes or has taken.
-
D.
plateNumberOf
Indicates the license plate number that is assigned to or associated with a particular vehicle.
-
E.
registrationNumber
Indicates the unique identifier assigned to an entity as part of an official or formal registration process.
- 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.