Triple
T17108311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Western Command |
E415156
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SWC |
E415156
|
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: SWC | Statement: [South Western Command, abbreviation, SWC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SWC Context triple: [South Western Command, abbreviation, SWC]
-
A.
SWC
SWC is the abbreviation for the Southwest Conference, a former NCAA Division I college athletic conference that primarily featured schools from Texas and the surrounding region.
-
B.
SWC
chosen
SWC is the acronym for the South Western Command of the Indian Army, a major operational command responsible for defense and military operations in India’s western sector.
-
C.
SWU
SWU is the commonly used abbreviation for Southwest University, a comprehensive higher education institution in China.
-
D.
SWD
SWD is the station code for Springwood railway station in New South Wales, Australia.
-
E.
SWM
SWM is the municipal utility company of Munich, Germany, responsible for providing services such as energy, water, and public transportation.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc2906a081909d0d43cf04319f52 |
completed | April 18, 2026, 7:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a013a019540819083ce6100b24f8cfb |
completed | May 11, 2026, 2:08 a.m. |
Created at: April 10, 2026, 5:35 a.m.