Triple
T8283464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D (vehicle registration code) |
E193734
|
entity |
| Predicate | codeLetter |
P7044
|
FINISHED |
| Object | D |
—
|
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: D | Statement: [D (vehicle registration code), codeLetter, D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeLetter Context triple: [D (vehicle registration code), codeLetter, D]
-
A.
alphabeticCode
chosen
Indicates that one entity is identified or represented by a specific alphabetic code assigned to it.
-
B.
letterOrNumberDesignation
Indicates that something is identified or labeled using a specific letter, number, or combination of both.
-
C.
letterSequence
Indicates that one sequence of letters directly follows or is ordered in relation to another within a larger string or alphabetic arrangement.
-
D.
alphabet
Indicates that one entity is an alphabet or set of symbols used for representing elements (such as characters or tokens) in relation to another entity.
-
E.
codeword
Indicates that one entity serves as a codeword or encoded representation used to convey, reference, or stand in for another entity within a coding or communication system.
- 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_69ca82e217a48190880695635c44b2ed |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7aceec8881909cdfa488dfedc0f5 |
completed | March 31, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69cb70ad9fc081908741f8c4a4141edf |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:52 p.m.