Triple
T26470973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sneath Lane trailhead |
E665897
|
entity |
| Predicate | historicalAccessTo |
P104247
|
FINISHED |
| Object | Nike missile site SF-51 |
—
|
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: Nike missile site SF-51 | Statement: [Sneath Lane trailhead, historicalAccessTo, Nike missile site SF-51]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalAccessTo Context triple: [Sneath Lane trailhead, historicalAccessTo, Nike missile site SF-51]
-
A.
historicallyProvidedAccessTo
chosen
Indicates that one entity, in the past, enabled or allowed another entity to access a resource, service, location, or information.
-
B.
historicalPass
Indicates that an entity has successfully completed or passed a historical event, period, or examination related to history.
-
C.
hasHistoricalContext
Indicates that something is related to, influenced by, or best understood in light of specific past events, conditions, or time periods.
-
D.
historicalRecord
Indicates that there exists a documented account or record capturing information about an entity, event, or relationship from the past.
-
E.
historicalResource
Indicates that a resource has historical significance or relevance, typically documenting or representing past events, conditions, or contexts.
- 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_69ee883f80dc819090e311b022b78e02 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: April 27, 2026, 12:19 a.m.