Triple
T14430633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assiniboine |
E357816
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Hohe |
E955580
|
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: Hohe | Statement: [Assiniboine, alsoKnownAs, Hohe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hohe Context triple: [Assiniboine, alsoKnownAs, Hohe]
-
A.
Hohe
chosen
Hohe is an alternative name for the Assiniboine language, a Siouan language traditionally spoken by the Assiniboine people of North America.
-
B.
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.
-
C.
Hoher Meißner
Hoher Meißner is a prominent low mountain massif in northern Hesse, Germany, known for its forested plateau, scenic views, and cultural significance in regional folklore.
-
D.
Schneidhain
Schneidhain is a district of the town Königstein im Taunus in the Hochtaunus region of Hesse, Germany.
-
E.
Fürth Hardhöhe
Fürth Hardhöhe is a station in the city of Fürth that serves as the western terminus of a line on the Nuremberg U-Bahn rapid transit system.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de914570f08190b1c7c1c57a0cb476 |
completed | April 14, 2026, 7:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd5bd3e6c48190b4fc3794202a0c3f |
completed | May 8, 2026, 3:43 a.m. |
Created at: April 10, 2026, 1:18 a.m.