Triple
T8370845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HLLB |
E197448
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Benina |
E199595
|
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: Benina | Statement: [HLLB, namedAfter, Benina]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Benina Context triple: [HLLB, namedAfter, Benina]
-
A.
Benina
chosen
Benina is a town in eastern Libya that serves as the main gateway to the nearby city of Benghazi through its international airport.
-
B.
Maroua
Maroua is a prominent city in northern Cameroon known as a regional commercial and cultural center near the Sahel.
-
C.
Mbouda
Mbouda is a significant urban center in western Cameroon known for its role as a commercial and administrative hub in the region.
-
D.
Ewondo
Ewondo is a Bantu language spoken primarily by the Ewondo people in central Cameroon, including in and around the capital city, Yaoundé.
-
E.
Eyamba
Eyamba is a prominent clan of the Efik people of southeastern Nigeria, historically associated with leadership and influence in the Old Calabar region.
- 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_69ca82f56730819080cec5d991c76f4c |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80a509dc81909e0ea4c66b21d84f |
completed | March 31, 2026, 8:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cdc79752b48190933ea644a59f2305 |
completed | April 2, 2026, 1:34 a.m. |
Created at: March 30, 2026, 6:01 p.m.