Triple
T18329009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seattle Thunderbirds |
E439084
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SEA |
—
|
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: SEA | Statement: [Seattle Thunderbirds, abbreviation, SEA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SEA Context triple: [Seattle Thunderbirds, abbreviation, SEA]
-
A.
SEA
SEA is the high-speed rail line designation used for the LGV Sud Europe Atlantique route in France.
-
B.
SEA
SEA is an educational organization that offers ocean-focused study abroad and research programs combining marine science, environmental studies, and sailing experience.
-
C.
SEA
chosen
SEA is the three-letter IATA airport code for Seattle–Tacoma International Airport, the primary commercial airport serving the Seattle metropolitan area in Washington, USA.
-
D.
SEA
SEA is the commonly used abbreviation for the Single European Act, a landmark 1986 treaty that significantly advanced European Community integration and paved the way for the single market.
-
E.
SEA
SEA is the National Rail station code assigned to Seaham railway station in County Durham, England.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aaceb4c81909c4a6b2790602d2e |
completed | April 19, 2026, 5:02 p.m. |
Created at: April 10, 2026, 10:36 a.m.