Triple
T19617855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vehicle registration plates of the Czech Republic |
E470913
|
entity |
| Predicate | standardHeight |
P9788
|
FINISHED |
| Object | approximately 110 millimetres |
—
|
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: approximately 110 millimetres | Statement: [Vehicle registration plates of the Czech Republic, standardHeight, approximately 110 millimetres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardHeight Context triple: [Vehicle registration plates of the Czech Republic, standardHeight, approximately 110 millimetres]
-
A.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
-
B.
heightDescription
Indicates how tall an entity is, typically expressed in descriptive or qualitative terms rather than a precise measurement.
-
C.
standardPar
Indicates that two entities are parallel and conform to a recognized or defined standard of parallelism.
-
D.
hasHeight
chosen
Indicates that one entity possesses a specific vertical measurement or stature.
-
E.
originalHeight
Indicates the initial or starting height of an entity before any change, adjustment, or transformation occurs.
- 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640e346548190b12e38d716bdfc4f |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.