Triple
T1839030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zugspitze |
E41130
|
entity |
| Predicate | hasObservationPlatform |
P13017
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Zugspitze, hasObservationPlatform, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasObservationPlatform Context triple: [Zugspitze, hasObservationPlatform, yes]
-
A.
hasObservationSite
Indicates that something (such as a measurement, event, or observation activity) is associated with or took place at a specific observation site or location.
-
B.
hasViewingPlatform
chosen
Indicates that an entity includes or is equipped with a designated platform or area intended for viewing or observing something.
-
C.
hasObservation
Indicates that an entity records, contains, or is associated with a specific observation or measured instance.
-
D.
isObservedOn
Indicates that a particular phenomenon, condition, or attribute is detected or recorded at a specific time, date, or occasion.
-
E.
hasIslandPlatforms
Indicates that the subject has one or more island-style platforms, typically positioned between tracks and accessible from both sides.
- F. None of above.
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_69a88647f9388190909bc36e795bdaec |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafd88ebc81908208394746351fe6 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.