Triple
T8004557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Täschhorn |
E186331
|
entity |
| Predicate | toponymRefersTo |
P80275
|
FINISHED |
| Object | village of Täsch |
—
|
LITERAL 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: village of Täsch | Statement: [Täschhorn, toponymRefersTo, village of Täsch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toponymRefersTo Context triple: [Täschhorn, toponymRefersTo, village of Täsch]
-
A.
toponymLiteralMeaning
Indicates the literal or etymological meaning of a place name (toponym), describing what the name directly translates to or signifies.
-
B.
hasNotableToponym
Indicates that an entity is associated with a place name that is particularly notable, distinctive, or significant.
-
C.
hasToponymy
Indicates a relationship where one entity possesses or is associated with the system, study, or set of place names (toponyms) of another entity.
-
D.
replacedByToponym
Indicates that one name or designation has been superseded and is now represented or referred to by a toponym (a place-based name).
-
E.
toponymSourceFor
Indicates that one entity serves as the origin, basis, or source from which another entity’s place name (toponym) is derived.
- F. None of above. chosen
Provenance (4 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_69ca82aaaf24819084b94d18f699ba53 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3cf5fb588190ada4ec7d8087619c |
completed | March 31, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69cb0483d3b48190b250c7603d747bca |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bbbacc81909c6cf8ec35314bbb |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:18 p.m.