Triple
T13528662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campeonato Brasileiro de Futebol Feminino |
E323075
|
entity |
| Predicate | fifaCode |
P6278
|
FINISHED |
| Object | BRA |
E107120
|
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: BRA | Statement: [Campeonato Brasileiro de Futebol Feminino, fifaCode, BRA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BRA Context triple: [Campeonato Brasileiro de Futebol Feminino, fifaCode, BRA]
-
A.
BRA
chosen
BRA is the three-letter ISO 3166-1 alpha-3 country code that uniquely identifies Brazil in international standards and data systems.
-
B.
BR
BR is the IATA airline designator for EVA Air, a major Taiwanese international carrier based in Taoyuan.
-
C.
BR
BR is a postcode area in southeast London and parts of northwest Kent, covering towns such as Bromley and Beckenham.
-
D.
BR
BR is the official station code used to identify Burlington GO Station in Ontario, Canada.
-
E.
BR
BR is the upper house of Austria’s parliament, representing the federal states in the legislative process.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafb8e0cc8190b47f6aeb8ced470e |
completed | April 12, 2026, 2:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f75d95ce008190a915fe5865c38ee5 |
completed | May 3, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:44 p.m.