Triple
T7146087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Alsberg |
E166571
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Alsberg |
E166571
|
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: Alsberg | Statement: [Henry Alsberg, familyName, Alsberg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alsberg Context triple: [Henry Alsberg, familyName, Alsberg]
-
A.
Alsberg
chosen
Alsberg is a surname of Germanic origin borne by various notable individuals, including American writer and theater director Henry Alsberg.
-
B.
Alpspitze
Alpspitze is a prominent pyramid-shaped peak in the Bavarian Alps of Germany, popular for hiking, climbing, and skiing.
-
C.
Hoche
Hoche is a Paris Métro station located in the northeastern suburb of Pantin, serving as a stop on the city’s Line 5.
-
D.
Berghaupten
Berghaupten is a small municipality in the Ortenau district of Baden-Württemberg in southwestern Germany, known for its scenic location in the Black Forest region.
-
E.
Bärenkopf
Bärenkopf is a mountain peak in the Austrian Alps that forms part of the Glockner Group.
- 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_69c6888579d481909e05a8d6b81bf733 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7d3c48c8190a71a61a1d50cd7da |
completed | March 27, 2026, 8:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7ada12a848190b6e98e0b1a258c17 |
completed | March 28, 2026, 10:29 a.m. |
Created at: March 27, 2026, 2:46 p.m.