Triple
T35933362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mapleton Falls National Park |
E1039227
|
entity |
| Predicate | lookoutName |
P161856
|
FINISHED |
| Object | Mapleton Falls Lookout |
—
|
NE NERFINISHED |
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: Mapleton Falls Lookout | Statement: [Mapleton Falls National Park, lookoutName, Mapleton Falls Lookout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lookoutName Context triple: [Mapleton Falls National Park, lookoutName, Mapleton Falls Lookout]
-
A.
hasLookout
Indicates that one entity serves as a lookout or watchful observer for another entity, monitoring for potential events, threats, or changes.
-
B.
hasLookoutStructure
Indicates that one entity possesses or includes a structure specifically intended for observing or monitoring an area.
-
C.
lighthouseName
Indicates that a lighthouse is identified by a specific name.
-
D.
hasOverlookName
chosen
Indicates that an entity (such as a viewpoint or location) has a specific name used to identify it as an overlook or scenic vantage point.
-
E.
observationPlatform
Indicates that one entity serves as the physical or virtual platform, site, or facility from which observations of another entity or phenomenon are made.
- 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_69f76e23e4688190a5369138755138bf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.