Triple
T23498513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corumbá |
E571768
|
entity |
| Predicate | hasUNLOCODE |
P1492
|
FINISHED |
| Object | BRCOB |
—
|
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: BRCOB | Statement: [Corumbá, hasUNLOCODE, BRCOB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BRCOB Context triple: [Corumbá, hasUNLOCODE, BRCOB]
-
A.
BRCOB
chosen
BRCOB is the UN/LOCODE identifying the Brazilian river port city of Corumbá, an important logistics hub near the Bolivia border.
-
B.
BRC
BRC is the vehicle registration code used for the city of Brčko in Bosnia and Herzegovina.
-
C.
BRC
BRC is an abbreviation commonly used to refer to a Board Risk Committee, the governing body responsible for overseeing an organization’s risk management framework and policies.
-
D.
BRC
BRC is a major Hungarian life sciences research institute in Szeged known for its work in molecular biology, genetics, biochemistry, and related fields.
-
E.
BRC
BRC is the railway station code for Vadodara Junction, a major rail hub in the Indian state of Gujarat.
- 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_69e245b4829881909b77a70e942bbd54 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7e184ec8190aff3677c9b00a8f2 |
completed | April 29, 2026, 6:40 a.m. |
Created at: April 17, 2026, 6:06 p.m.