Triple
T33969922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoher Ifen |
E870961
|
entity |
| Predicate | hasPlateauName |
P193074
|
FINISHED |
| Object | Gottesacker plateau |
—
|
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: Gottesacker plateau | Statement: [Hoher Ifen, hasPlateauName, Gottesacker plateau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlateauName Context triple: [Hoher Ifen, hasPlateauName, Gottesacker plateau]
-
A.
hasPlateaus
Indicates that something possesses or contains one or more plateau-like flat elevated areas.
-
B.
hasPlateauSize
Indicates that an entity possesses or is characterized by a specific plateau size, typically referring to the extent or magnitude of a flat or stable region.
-
C.
hasCliffName
Indicates that an entity (such as a cliff or related feature) is associated with a specific name assigned to that cliff.
-
D.
hasNearbyPlateau
Indicates that one geographic entity is located close to or adjacent to a plateau.
-
E.
hasMajorPlateau
Indicates that an entity possesses or includes a primary, extensive plateau as a significant geographic or structural feature.
- 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_69f3499ce8e88190b66e1d49ad8c7037 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69fd37b45b4481908b947b52fbcb7ade |
completed | May 8, 2026, 1:09 a.m. |
Created at: May 1, 2026, 1:50 a.m.