Triple
T7405572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Quebrada cliff divers |
E170860
|
entity |
| Predicate | performType |
P63774
|
FINISHED |
| Object | cliff diving |
—
|
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: cliff diving | Statement: [La Quebrada cliff divers, performType, cliff diving]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performType Context triple: [La Quebrada cliff divers, performType, cliff diving]
-
A.
typeOfPerformances
chosen
Indicates the kinds or categories of performances associated with or offered by an entity.
-
B.
performanceClass
Indicates the category or level of performance to which an entity is assigned, typically reflecting its capabilities or quality tier.
-
C.
performsAs
Indicates that one entity takes on, enacts, or fulfills the role, function, or character of another entity.
-
D.
typicalPerformance
Indicates the usual or characteristic level at which an entity performs under normal conditions.
-
E.
performerType
Indicates the role or category of performer responsible for carrying out an action or participating in an event.
- 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_69c68a6010108190925e5284de022660 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f271f1d481909a46d50b13b51a62 |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f0323b2c819098ab72c33e6d8534 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:10 p.m.