Triple
T13140493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DL |
E312197
|
entity |
| Predicate | codeFormatPosition |
P93307
|
FINISHED |
| Object | prefix on Indian license plates |
—
|
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: prefix on Indian license plates | Statement: [DL, codeFormatPosition, prefix on Indian license plates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeFormatPosition Context triple: [DL, codeFormatPosition, prefix on Indian license plates]
-
A.
coordinateFormat
Indicates the specific representation or notation used to express a set of coordinates.
-
B.
hasSourcePosition
Indicates that something originates from, is located at, or is associated with a specific source position or starting point.
-
C.
lineNumberOrCode
chosen
Indicates the specific line number or code identifier associated with an element, reference, or occurrence within a structured sequence or document.
-
D.
classPosition
Indicates the relative ordering or rank of an entity within a class, group, or sequence.
-
E.
positionInProgram
Indicates the specific place or order that something occupies within a larger program or sequence of program elements.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d981b84f1081908b9e2d54a64d4c2d |
completed | April 10, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69d9804543cc8190a23cd7da59a12a7b |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:10 p.m.