Triple
T5978315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal District (Brazil) |
E133055
|
entity |
| Predicate | ISO3166-2Code |
P208
|
FINISHED |
| Object | BR-DF |
E541825
|
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: BR-DF | Statement: [Federal District (Brazil), ISO3166-2Code, BR-DF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BR-DF Context triple: [Federal District (Brazil), ISO3166-2Code, BR-DF]
-
A.
BR-DF
chosen
BR-DF is the ISO 3166-2 code representing Brazil’s Federal District, which contains the national capital, Brasília.
-
B.
BR2
BR2 is a UK postcode district covering parts of Hayes and surrounding areas in the London Borough of Bromley in southeast England.
-
C.
BDF
The BDF is the national military organization of the Kingdom of Bahrain, responsible for the country's defense and security.
-
D.
BRL
BRL is the official currency code for the Brazilian real, the legal tender of Brazil.
-
E.
BRD
BRD is the IATA airport code for Brainerd Lakes Regional Airport, a public airport serving the Brainerd area in Minnesota, United States.
- 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_69c0086f45e8819098f73dd16d45ec9d |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04a3e686c81908910c0881ac1624d |
completed | March 22, 2026, 7:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0e4184a708190a9e4fe8453463a4b |
completed | March 23, 2026, 6:56 a.m. |
Created at: March 22, 2026, 4:04 p.m.