Triple
T18469361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osbern |
E451251
|
entity |
| Predicate | hasComponent |
P35
|
FINISHED |
| Object | bern |
—
|
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: bern | Statement: [Osbern, hasComponent, bern]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: bern Context triple: [Osbern, hasComponent, bern]
-
A.
bern
chosen
Bern is the de facto capital city of Switzerland, known for its well-preserved medieval old town and status as the country's political center.
-
B.
Ber
Ber is a traditional Yiddish given name, often associated with Ashkenazi Jewish men and sometimes used as a counterpart to the Hebrew name Dov.
-
C.
BER
BER is a U.S. Department of Energy research program that advances fundamental science on biological systems and environmental processes to address energy and climate challenges.
-
D.
BER
BER is Berlin Brandenburg Airport, the main international airport serving Germany’s capital region.
-
E.
BER
BER is the ICAO airline designator formerly used by the now-defunct German carrier Air Berlin.
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5305e349c8190925166bc3dddb320 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 11:34 a.m.