Triple
T21511764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buhlois |
E530741
|
entity |
| Predicate | locatedInAdministrativeTerritorialEntity |
P40
|
FINISHED |
| Object | Buhl |
—
|
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: Buhl | Statement: [Buhlois, locatedInAdministrativeTerritorialEntity, Buhl]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Buhl Context triple: [Buhlois, locatedInAdministrativeTerritorialEntity, Buhl]
-
A.
Buhl
Buhl is a German-language surname most notably associated with Austrian mountaineer Hermann Buhl, famed for his pioneering ascents in the Himalayas.
-
B.
Buhl
chosen
Buhl is a commune in northeastern France’s Grand Est region, known for its historic Saint-Jean-Baptiste church and picturesque setting in the Alsace area.
-
C.
Scobey
Scobey is a surname and place name most notably associated with the city of Scobey in Montana, United States.
-
D.
Binger
Binger is the term used to refer to inhabitants of the German town of Bingen am Rhein.
-
E.
Hulett
Hulett was a South African company that became part of the diversified agribusiness and sugar producer Tongaat Hulett through a corporate merger.
- 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_69e0c45c81f08190a6b8bbb70a45aae7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea863b18819080e3ff249b10ec28 |
completed | April 23, 2026, 9:46 a.m. |
Created at: April 16, 2026, 6:25 p.m.