Triple
T11623254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blaubeuren |
E276192
|
entity |
| Predicate | hasNearbyCaveSite |
P73138
|
FINISHED |
| Object | prehistoric caves of the Swabian Jura |
—
|
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: prehistoric caves of the Swabian Jura | Statement: [Blaubeuren, hasNearbyCaveSite, prehistoric caves of the Swabian Jura]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyCaveSite Context triple: [Blaubeuren, hasNearbyCaveSite, prehistoric caves of the Swabian Jura]
-
A.
hasNearbyCave
chosen
Indicates that one entity is located close to or in the vicinity of a cave associated with another entity.
-
B.
hasCaves
Indicates that one entity possesses, contains, or is characterized by the presence of caves.
-
C.
hasApproximateNumberOfCaves
Indicates that an entity is associated with an estimated or non-exact number of caves.
-
D.
isShowCave
Indicates that a cave or cavern is being displayed, revealed, or made visible within a given context or environment.
-
E.
hasNearbyArchaeologicalSite
Indicates that an entity is located close to or in the vicinity of an archaeological site.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a122a3708190ab6513dad4c4fde7 |
completed | April 10, 2026, 7:05 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:39 p.m.