Triple
T5322885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Grotto |
E121714
|
entity |
| Predicate | hasCliffJumping |
P63488
|
FINISHED |
| Object | unofficial and potentially dangerous activity |
—
|
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: unofficial and potentially dangerous activity | Statement: [The Grotto, hasCliffJumping, unofficial and potentially dangerous activity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCliffJumping Context triple: [The Grotto, hasCliffJumping, unofficial and potentially dangerous activity]
-
A.
hasCliff
Indicates that something possesses or features a steep, high rock face or abrupt vertical drop as part of its structure or environment.
-
B.
hasSkyJumpAttraction
Indicates that an entity features or includes a sky jump attraction as one of its offerings or components.
-
C.
hasCliffHeight
Indicates the relationship between a cliff and the measurement of its vertical height.
-
D.
hasCliffs
Indicates that something possesses or is characterized by the presence of cliffs.
-
E.
canClimb
Indicates that one entity has the ability or permission to climb another entity or surface.
- 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_69bd463d956c819088105c3db802c017 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd86f20f008190be7b5848af05f2b8 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd84561c7081909e5937c7816e492c |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd86f0cbfc8190b6665dd9b28d6345 |
completed | March 20, 2026, 5:42 p.m. |
Created at: March 20, 2026, 1:59 p.m.