Triple
T34785840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hull Trains |
E1002801
|
entity |
| Predicate | trackAccessType |
P51863
|
FINISHED |
| Object | open-access |
—
|
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: open-access | Statement: [Hull Trains, trackAccessType, open-access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackAccessType Context triple: [Hull Trains, trackAccessType, open-access]
-
A.
trackAccess
Indicates that one entity monitors, records, or keeps a log of another entity’s access or usage of a resource.
-
B.
typeOfAccess
chosen
Indicates the specific kind or level of access that one entity has to another (such as read, write, or execute permissions).
-
C.
accessIs
Indicates that one entity has the ability, permission, or means to reach, use, or interact with another entity or resource.
-
D.
accessDeterminedBy
Indicates that the ability to access a resource is governed or controlled by a specified condition, rule, or authority.
-
E.
accessRestriction
Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
- 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.