Triple
T19970994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgium at the Olympic Games |
E480072
|
entity |
| Predicate | NOCCode |
P39350
|
FINISHED |
| Object | BEL |
—
|
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: BEL | Statement: [Belgium at the Olympic Games, NOCCode, BEL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BEL Context triple: [Belgium at the Olympic Games, NOCCode, BEL]
-
A.
BEL
BEL is the ICAO airline designator used to identify Brussels Airlines in international aviation operations.
-
B.
BEL
BEL is the IATA airport code for the main airport serving Belém in the state of Pará, Brazil.
-
C.
BEL
BEL is the standard abbreviation used to represent the Belleville Bulls, a former junior ice hockey team in the Ontario Hockey League.
-
D.
BEL
chosen
BEL is the three-letter ISO 3166-1 alpha-3 country code that uniquely identifies Belgium in international standards and data systems.
-
E.
BEL
BEL is the commonly used abbreviation for Bharat Electronics Limited, an Indian state-owned aerospace and defense electronics company.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65bc9694881909a31841702ab9e5f |
completed | April 20, 2026, 5 p.m. |
Created at: April 10, 2026, 1:54 p.m.