Triple
T11089659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landscape Arch |
E262216
|
entity |
| Predicate | notableRockfallEvent |
P68329
|
FINISHED |
| Object | large rock slab collapse in the 1990s |
—
|
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: large rock slab collapse in the 1990s | Statement: [Landscape Arch, notableRockfallEvent, large rock slab collapse in the 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRockfallEvent Context triple: [Landscape Arch, notableRockfallEvent, large rock slab collapse in the 1990s]
-
A.
hadMajorRockfall
chosen
Indicates that a significant rockfall event has occurred at or affected the subject entity.
-
B.
notableGorge
Indicates a relationship where a gorge is recognized as notable, significant, or of particular interest in some context.
-
C.
notableEarthquake
Indicates that an earthquake event is significant or noteworthy due to its magnitude, impact, or historical importance.
-
D.
naturalCaveCollapsed
Indicates that a naturally formed cave has undergone a structural failure resulting in its partial or complete collapse.
-
E.
triggeredLandslides
Indicates that one entity caused or initiated landslides affecting another entity or area.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799e96ca08190838c8a04d1eb2a16 |
completed | April 9, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_69d744185a5881909ba4cf151d1798ec |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.