Triple
T36818309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aguinid Falls |
E909806
|
entity |
| Predicate | hasLevelCountUsedInTours |
P196923
|
FINISHED |
| Object | 5 to 8 levels depending on route |
—
|
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: 5 to 8 levels depending on route | Statement: [Aguinid Falls, hasLevelCountUsedInTours, 5 to 8 levels depending on route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLevelCountUsedInTours Context triple: [Aguinid Falls, hasLevelCountUsedInTours, 5 to 8 levels depending on route]
-
A.
hasTouringReputation
Indicates that an entity is recognized or reputed for its activities, performance, or presence while traveling or touring.
-
B.
hasTourAccess
Indicates that an entity is permitted to enter or participate in a specified tour.
-
C.
hasTournamentLevel
Indicates that an entity participates in or is classified by a specific competitive or organizational level within a tournament structure.
-
D.
hasTourElement
Indicates that something includes or is associated with a specific element or component of a tour.
-
E.
hasTourHistory
Indicates that an entity has a record of past tours or tour-related activities.
- 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_69f76e7dd13c81908c60b05adb49eeb5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
| PDg | Predicate description generation | batch_69fe6e4801108190a6be6bec2d52a1b9 |
completed | May 8, 2026, 11:14 p.m. |
Created at: May 3, 2026, 4:13 p.m.