Triple
T17481885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wimsener Höhle |
E425679
|
entity |
| Predicate | hasExploredLength |
P126230
|
FINISHED |
| Object | several hundred metres |
—
|
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: several hundred metres | Statement: [Wimsener Höhle, hasExploredLength, several hundred metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExploredLength Context triple: [Wimsener Höhle, hasExploredLength, several hundred metres]
-
A.
exploredLength
chosen
Indicates the measured extent or distance of something that has been explored or traversed.
-
B.
exploredWith
Indicates that one entity explored something together with another entity as companions or partners in the exploration.
-
C.
hasExploration
Indicates that one entity engages in, is associated with, or possesses an activity or process of exploration in relation to another entity or context.
-
D.
exploredDuring
Indicates that an entity was explored or investigated within the time frame or context of a specified event or period.
-
E.
hasTrailLength
Indicates that an entity (such as a trail or route) has a specific measured length.
- 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451c0db14819098922453131fb40a |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.