Triple
T3857974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bilen |
E90064
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Bogos |
E392872
|
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: Bogos | Statement: [Bilen, hasAlternativeName, Bogos]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bogos Context triple: [Bilen, hasAlternativeName, Bogos]
-
A.
Bogo
chosen
Bogo is an alternative name for the Bilen people, an ethnic group primarily living in Eritrea.
-
B.
Bozeat
Bozeat is a rural village and civil parish in Northamptonshire, England, known for its historic church and traditional English countryside setting.
-
C.
BOG
BOG is the IATA airport code for El Dorado International Airport, the main international gateway serving Bogotá, Colombia.
-
D.
Boebe
Boebe was an ancient town in the region of Magnesia in Thessaly, Greece, known from classical sources and associated with nearby Lake Boebeis.
-
E.
Bou
Bou is a surname of Spanish origin borne by Argentine professional footballer Gustavo Bou, among others.
- 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_69aed95b3c088190a8f85d19e6070599 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec1e68f88190941c39221486f6ae |
completed | March 9, 2026, 3:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b51231608c8190bbc5dc990fba1606 |
completed | March 14, 2026, 7:45 a.m. |
Created at: March 9, 2026, 3:19 p.m.