Triple
T20060219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marmore Falls |
E499448
|
entity |
| Predicate | hasOperatingSchedule |
P10068
|
FINISHED |
| Object | water released at specific times for visitors |
—
|
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: water released at specific times for visitors | Statement: [Marmore Falls, hasOperatingSchedule, water released at specific times for visitors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOperatingSchedule Context triple: [Marmore Falls, hasOperatingSchedule, water released at specific times for visitors]
-
A.
hasWorkSchedule
Indicates that an entity is assigned or follows a specific work schedule, defining when they are expected to work.
-
B.
hasAdministrationSchedule
Indicates that there is a defined plan or timetable specifying when and how an entity is to be administered or given.
-
C.
operatesAtTime
Indicates that an action, process, or system is functioning or active during a specified time or time interval.
-
D.
hoursOfOperation
chosen
Indicates the time periods during which a place or service is open and available for use.
-
E.
has24HourOperations
Indicates that an entity operates continuously for 24 hours a day without closing.
- 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66374f4a48190beb575a6c84ebdb4 |
completed | April 20, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:38 p.m.