Triple
T22874624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Society of Women Engineers |
E567289
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SWE |
—
|
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: SWE | Statement: [Society of Women Engineers, abbreviation, SWE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SWE Context triple: [Society of Women Engineers, abbreviation, SWE]
-
A.
SWE
chosen
SWE is the three-letter ISO 3166-1 alpha-3 country code representing Sweden.
-
B.
SDE
SDE is the IATA airport code for the main airport serving Santiago del Estero in northern Argentina.
-
C.
SWEAP
SWEAP is a scientific instrument suite on NASA’s Parker Solar Probe designed to measure the solar wind’s particles and plasma properties near the Sun.
-
D.
SWC
SWC is a high-performance JavaScript and TypeScript compiler and bundler written in Rust, often used as a fast alternative to Babel in modern web development workflows.
-
E.
SWC
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.
- 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_69e24589d8348190b96422d13a678bc1 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f56d6448190ada4aef08eac2bed |
completed | April 29, 2026, 3:47 a.m. |
Created at: April 17, 2026, 3:39 p.m.