Triple
T36901642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rage |
E912049
|
entity |
| Predicate | steepDrop |
P186667
|
FINISHED |
| Object | beyond-vertical first drop |
—
|
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: beyond-vertical first drop | Statement: [Rage, steepDrop, beyond-vertical first drop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: steepDrop Context triple: [Rage, steepDrop, beyond-vertical first drop]
-
A.
verticalDrop_m
Indicates the vertical distance, measured in meters, through which something drops or falls from a higher point to a lower point.
-
B.
blowsDownSlopeOf
Indicates that something (typically wind or air) moves or exerts force downward along the incline or gradient of a slope relative to another entity.
-
C.
dropsFrom
Indicates that one entity falls, descends, or is released from another entity as its source or origin.
-
D.
risesSteeplyFrom
Indicates that one entity ascends sharply or abruptly upward starting from the position or level of another entity.
-
E.
waterfallDrop
Indicates a vertical or near-vertical descent of water from a higher level to a lower level, as in a waterfall.
- 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_69f76e841b54819097e7fa768bbc70b2 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:13 p.m.