Triple
T30238797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Cruz, Big Trees and Pacific Railway |
E768848
|
entity |
| Predicate | openedForTouristOperations |
P180962
|
FINISHED |
| Object | 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: 20th century | Statement: [Santa Cruz, Big Trees and Pacific Railway, openedForTouristOperations, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForTouristOperations Context triple: [Santa Cruz, Big Trees and Pacific Railway, openedForTouristOperations, 20th century]
-
A.
openedAsTouristOperation
chosen
Indicates that an entity began functioning or was inaugurated specifically as a tourist-oriented operation or attraction.
-
B.
openedAsTouristSite
Indicates that a place or structure has been made accessible and designated for visitation by tourists.
-
C.
tourOpened
Indicates that a tour has begun or been made available for participation or viewing.
-
D.
operatesTouristAttraction
Indicates that an entity manages and runs the day-to-day operations of a tourist attraction.
-
E.
openedAttraction
Indicates that an entity initiated the operation or public availability of an attraction at a specific time or 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_69f224820c048190b1435c4cc145acf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 29, 2026, 7:38 p.m.