Triple
T22664630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birmingham Bulls |
E559750
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | BIR |
—
|
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: BIR | Statement: [Birmingham Bulls, abbreviation, BIR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BIR Context triple: [Birmingham Bulls, abbreviation, BIR]
-
A.
BIR
chosen
BIR is the standard abbreviation used for the former World Hockey Association team, the Birmingham Bulls.
-
B.
BIR
BIR is a German vehicle registration code assigned to the district of Birkenfeld in the state of Rhineland-Palatinate.
-
C.
BIR
BIR is a former short-track auto racing facility located near the Birmingham–Shuttlesworth International Airport in Birmingham, Alabama.
-
D.
BIRK
BIRK is the ICAO airport code for Reykjavík Airport, the main domestic and regional airport serving Iceland’s capital city.
-
E.
BIRPI
BIRPI was an early international organization responsible for administering treaties on the protection of industrial property, which later evolved into the World Intellectual Property Organization (WIPO).
- 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1781b3dbc8190a312843cf8c1bfc6 |
completed | April 29, 2026, 3:16 a.m. |
Created at: April 17, 2026, 3:08 p.m.