Triple
T37332640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tahquitz Canyon |
E926793
|
entity |
| Predicate | hasWaterfallName |
P99642
|
FINISHED |
| Object | Tahquitz Falls |
—
|
NE NERFINISHED |
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: Tahquitz Falls | Statement: [Tahquitz Canyon, hasWaterfallName, Tahquitz Falls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaterfallName Context triple: [Tahquitz Canyon, hasWaterfallName, Tahquitz Falls]
-
A.
hasWaterfall
Indicates that one entity possesses, contains, or features a waterfall associated with it.
-
B.
hasWaterfallType
Indicates that one entity is characterized by or associated with a specific type or classification of waterfall.
-
C.
waterfallName
chosen
Indicates that an entity is identified by or associated with the specific name of a waterfall.
-
D.
hasBasinNamed
Indicates that an entity possesses or is associated with a basin that has a specified name.
-
E.
waterfallNameEtymology
Indicates the origin or reasoning behind the name given to a particular waterfall.
- 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: May 3, 2026, 4:16 p.m.