Triple
T20105256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knockbreck |
E490150
|
entity |
| Predicate | nearbySettlement |
P350
|
FINISHED |
| Object | Stein |
—
|
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: Stein | Statement: [Knockbreck, nearbySettlement, Stein]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Stein Context triple: [Knockbreck, nearbySettlement, Stein]
-
A.
Stein
Stein is a German-origin surname borne by numerous notable individuals across fields such as exploration, philosophy, literature, and politics.
-
B.
Stein
Stein is a municipality in the Dutch province of Limburg, known for its industrial heritage and location along the Meuse River near the Belgian border.
-
C.
Stein
chosen
Stein is a nearby settlement to Halistra, likely a small village or town in the same region.
-
D.
Stein (SG)
Stein (SG) is a municipality in the canton of St. Gallen in northeastern Switzerland, known for its rural Alpine setting and proximity to the Toggenburg region.
-
E.
Steinman
Steinman is a surname most notably associated with David B. Steinman, an influential American civil engineer and bridge designer.
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e666dbad30819082454f360f358131 |
completed | April 20, 2026, 5:48 p.m. |
Created at: April 11, 2026, 11:28 p.m.