Triple
T2319105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Victoria railway station |
E51135
|
entity |
| Predicate | hasStationCode |
P1289
|
FINISHED |
| Object | VIC |
E112300
|
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: [London Victoria railway station, hasStationCode, VIC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VIC Context triple: [London Victoria railway station, hasStationCode, VIC]
-
A.
VIC
chosen
VIC is the standard abbreviation for the Australian state of Victoria, commonly used in postal addresses and official contexts.
-
B.
Vin
Vin is a common shortened form of the given name Vincent, often used as an informal or familiar nickname.
-
C.
VIR
VIR is the ICAO airline designator used to identify Virgin Atlantic in international aviation operations.
-
D.
VELO
VELO is the high-precision vertex detector of the LHCb experiment at CERN, designed to measure particle trajectories very close to the proton–proton collision point.
-
E.
VEN
VEN is the three-letter ISO 3166-1 alpha-3 country code assigned to Venezuela for international identification and data standards.
- 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_69a88b074b908190ae983dbca7757d88 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc630b7ec819088735bde27fdabfe |
completed | March 7, 2026, 6:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae8966cc0c819092ad299645b0aa71 |
completed | March 9, 2026, 8:48 a.m. |
Created at: March 4, 2026, 7:49 p.m.