Triple
T5286260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss vehicle license plate |
E119625
|
entity |
| Predicate | mayDisplayCode |
P3746
|
FINISHED |
| Object | NE |
—
|
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: NE | Statement: [Swiss vehicle license plate, mayDisplayCode, NE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayDisplayCode Context triple: [Swiss vehicle license plate, mayDisplayCode, NE]
-
A.
mayPresent
Indicates that one entity is permitted or authorized to present, display, or introduce another entity or item.
-
B.
codeFor
chosen
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
-
C.
displayedWith
Indicates that one entity is shown or presented together alongside another entity in the same context or view.
-
D.
publiclyDisplayed
Indicates that something is shown or made visible in a public context or setting, accessible to people at large.
-
E.
maySign
Indicates that an entity has the permission or authority to sign a document, agreement, or similar item.
- 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_69bd446de5648190b313a90bd96730d2 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8c9c72b08190947b6b955ac1bb5a |
completed | March 20, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69bd844a56b48190ad743c42246e02dd |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:52 p.m.