Triple
T17541892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Sands Space Harbor |
E427217
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | WSH |
—
|
NE NERFINISHED |
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: WSH | Statement: [White Sands Space Harbor, IATAcode, WSH]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: WSH Context triple: [White Sands Space Harbor, IATAcode, WSH]
-
A.
WSH
WSH is the standard sports abbreviation for the Washington Commanders, the National Football League team based in the Washington, D.C. area.
-
B.
WSH
WSH is the stock ticker symbol for Willis Group Holdings, a global insurance brokerage and risk management firm.
-
C.
WSH
chosen
WSH is the location identifier for White Sands Space Harbor, a former NASA space shuttle landing site in New Mexico.
-
D.
WDS
WDS is the IATA airport code for Shiyan Wudangshan Airport, a regional airport serving the Shiyan and Wudangshan area in Hubei, China.
-
E.
WST
WST is an organization dedicated to advancing the interdisciplinary study and development of the World Wide Web and its impact on society.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4545e64448190a2a63bc13f549027 |
completed | April 19, 2026, 4:04 a.m. |
Created at: April 10, 2026, 5:49 a.m.