Triple
T243459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Fens |
E4983
|
entity |
| Predicate | isAccessibleFor |
P1017
|
FINISHED |
| Object | pedestrians |
—
|
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: pedestrians | Statement: [The Fens, isAccessibleFor, pedestrians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAccessibleFor Context triple: [The Fens, isAccessibleFor, pedestrians]
-
A.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
B.
hasAccessTo
chosen
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
-
C.
isGrantedFor
Indicates that a permission, right, or benefit has been formally given to a specific entity for a particular purpose or use.
-
D.
isProtectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
E.
hasAccessMode
Indicates the type or method of access that one entity is permitted to use with respect to 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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25dcd2b208190855d5d8d70a3acfc |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b62839c8190824064fe5da6a92a |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.