Triple
T25701974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarka Line |
E644487
|
entity |
| Predicate | promotesAccessTo |
P82958
|
FINISHED |
| Object | Tarka Trail area |
—
|
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: Tarka Trail area | Statement: [Tarka Line, promotesAccessTo, Tarka Trail area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotesAccessTo Context triple: [Tarka Line, promotesAccessTo, Tarka Trail area]
-
A.
assumesAccessTo
Indicates that one entity presupposes or takes for granted that it has access to another entity, resource, or piece of information.
-
B.
controlsAccessTo
Indicates that one entity regulates, manages, or determines the ability of another entity to reach, use, or interact with a resource, location, or service.
-
C.
improvesAccessToward
chosen
Indicates that one entity enhances or facilitates the ability of another entity to reach, use, or benefit from a resource, service, or opportunity.
-
D.
accessProvides
Indicates that one entity grants or enables the ability to use, enter, or retrieve another entity or resource.
-
E.
accessIs
Indicates that one entity has the ability, permission, or means to reach, use, or interact with 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 21, 2026, 8:47 p.m.