Triple
T30054097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taylor Creek Trail |
E763678
|
entity |
| Predicate | accessPointOf |
P120267
|
FINISHED |
| Object | Double Arch Alcove |
—
|
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: Double Arch Alcove | Statement: [Taylor Creek Trail, accessPointOf, Double Arch Alcove]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessPointOf Context triple: [Taylor Creek Trail, accessPointOf, Double Arch Alcove]
-
A.
isAccessPointOf
chosen
Indicates that one entity serves as an access point or entry interface through which another entity can be reached, used, or connected to.
-
B.
hasAccessPointFrom
Indicates that an entity can be reached or entered from a specific access point.
-
C.
accessPointRegion
Indicates the geographic or spatial region within which a given access point is located or operates.
-
D.
visitorAccessPoint
Indicates a location or interface through which visitors are allowed to enter, connect, or gain access to a place, system, or resource.
-
E.
modernAccessPoint
Indicates that an entity serves as a contemporary or up-to-date point of entry, connection, or interaction for accessing another entity or resource.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 29, 2026, 6:56 p.m.