Triple
T28167990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pagsanjan Falls |
E715378
|
entity |
| Predicate | tourismStarted |
P140799
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [Pagsanjan Falls, tourismStarted, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourismStarted Context triple: [Pagsanjan Falls, tourismStarted, early 20th century]
-
A.
tourismStartPeriod
chosen
Indicates the time period or date when a tourism-related activity, season, or service begins.
-
B.
beganDiversificationIntoTourism
Indicates that an entity started expanding its activities or operations into the tourism sector from a certain point in time.
-
C.
hasTourismDevelopment
Indicates that tourism-related infrastructure, services, or activities have been developed or promoted in relation to the referenced entity.
-
D.
touristServicesResumedYear
Indicates the year in which tourist services that were previously halted or disrupted began operating again.
-
E.
tourismBoom
Indicates a rapid and significant increase in tourism activity, such as visitor numbers, spending, or development, within a particular place or period.
- 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_69efd6b340f0819095680e15dcdc1830 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 10:11 p.m.