Triple
T36040481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R11 series |
E1042524
|
entity |
| Predicate | preservedCarNumber |
P194039
|
FINISHED |
| Object | 8013 |
—
|
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: 8013 | Statement: [R11 series, preservedCarNumber, 8013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preservedCarNumber Context triple: [R11 series, preservedCarNumber, 8013]
-
A.
notableVehicleNumber
Indicates that a specific vehicle is identified as notable or significant by a particular number or identifier.
-
B.
leadingCarNumber
Indicates the identifier or number assigned to the car that is currently in the leading position relative to others.
-
C.
carNumberUsed
Indicates that a specific car number has been used or assigned in a given context or event.
-
D.
registrationNumber
Indicates the unique identifier assigned to an entity as part of an official or formal registration process.
-
E.
hasCarNumberPreviously
Indicates that an entity has been associated with a specific car number at some earlier time before the current context.
- F. None of above. chosen
Provenance (4 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_69f76e2d7e8c8190bac4e90734566799 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
| PDg | Predicate description generation | batch_69fd5d47da488190a4f2dbd44a0a83b2 |
completed | May 8, 2026, 3:49 a.m. |
Created at: May 3, 2026, 4:07 p.m.