Triple
T4363905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burney Falls |
E98724
|
entity |
| Predicate | viewingFacilities |
P55786
|
FINISHED |
| Object | overlook |
—
|
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: overlook | Statement: [Burney Falls, viewingFacilities, overlook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewingFacilities Context triple: [Burney Falls, viewingFacilities, overlook]
-
A.
findingOnFacilities
Indicates a relationship where an inspection or assessment identifies a specific issue, observation, or result associated with particular facilities.
-
B.
associatedSpaceFacility
Indicates that there is a relationship linking an entity to a specific space-related facility with which it is connected or involved.
-
C.
servesFacility
Indicates that one entity provides services or support to a particular facility as its client, target, or area of operation.
-
D.
userFacility
Indicates a relationship where a user is associated with, has access to, or operates within a particular facility.
-
E.
hasFacilities
Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
- 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351e70a748190af6f1b709a0e75e6 |
completed | March 12, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff654308190b9717526120d80d3 |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:16 p.m.