Triple
T10297745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorsey station |
E241539
|
entity |
| Predicate | hasStationCode |
P1289
|
FINISHED |
| Object | DOR |
E349057
|
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: DOR | Statement: [Dorsey station, hasStationCode, DOR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DOR Context triple: [Dorsey station, hasStationCode, DOR]
-
A.
DOR
DOR is the standard abbreviation used for the Mexican football club Dorados de Sinaloa.
-
B.
DOR
chosen
DOR is the vehicle registration code used on license plates for the English county of Dorset.
-
C.
DOR
DOR is the California state agency that provides vocational rehabilitation and related services to help individuals with disabilities prepare for, obtain, and retain employment.
-
D.
Dor
Dor is the standard astronomical abbreviation for Dorado, a southern constellation named after the dolphinfish and known for containing part of the Large Magellanic Cloud.
-
E.
DUR
DUR is the IATA airport code for King Shaka International Airport serving Durban, South Africa.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2ed50908190962f0d6d049fb964 |
completed | April 7, 2026, 9:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d71d2cc9c48190bc36f6a4f8144b7f |
completed | April 9, 2026, 3:29 a.m. |
Created at: April 6, 2026, 11:43 a.m.