Triple
T16971127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria railway station |
E411681
|
entity |
| Predicate | hasStationCode |
P1289
|
FINISHED |
| Object | VIC |
E305742
|
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: VIC | Statement: [Victoria railway station, hasStationCode, VIC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VIC Context triple: [Victoria railway station, hasStationCode, VIC]
-
A.
VIC
chosen
VIC is the National Rail station code for London Victoria, a major central London railway terminus and Underground station.
-
B.
VIC
VIC is the standard abbreviation for the Australian state of Victoria, commonly used in postal addresses and official contexts.
-
C.
Vin
Vin is a common shortened form of the given name Vincent, often used as an informal or familiar nickname.
-
D.
V.I.C
V.I.C is an American rapper best known for his 2008 hit single "Get Silly" and his contributions to the snap music scene.
-
E.
VES
VES is an abbreviation for the Virtual Execution System, a runtime environment designed to execute managed code in a platform-independent manner.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0ad04ac81909a11b45be567613a |
completed | April 18, 2026, 6:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00d471d4248190acf40b6c11926a65 |
completed | May 10, 2026, 6:54 p.m. |
Created at: April 10, 2026, 5:31 a.m.