Triple
T5332522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sassnitz |
E123342
|
entity |
| Predicate | hasVehicleRegistrationCode |
P1173
|
FINISHED |
| Object | VR |
E511685
|
NE 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: VR | Statement: [Sassnitz, hasVehicleRegistrationCode, VR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VR Context triple: [Sassnitz, hasVehicleRegistrationCode, VR]
-
A.
VR
chosen
VR is a vehicle registration code used on license plates to identify vehicles registered in Bergen auf Rügen, Germany.
-
B.
VRG
VRG is the ICAO airline designator for Varig, the former Brazilian flag carrier and one of Latin America's historically significant airlines.
-
C.
Gear VR
Gear VR is a mobile virtual reality headset developed by Samsung in collaboration with Oculus, designed to work with select Samsung smartphones.
-
D.
Milk VR
Milk VR is a virtual reality content platform and studio known for producing immersive cinematic VR experiences.
-
E.
Daydream VR platform
Daydream VR platform was Google’s mobile virtual reality ecosystem built into Android, offering a standardized hardware and software platform for immersive VR experiences on compatible smartphones and headsets.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69bd46477f9081909d242a327d749466 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85aab0308190990626cbc9da3e21 |
completed | March 20, 2026, 5:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf21bebea0819083e6deae67f3e834 |
completed | March 21, 2026, 10:54 p.m. |
Created at: March 20, 2026, 2 p.m.