Triple
T33495038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newlands Forest |
E857841
|
entity |
| Predicate | accessFromRoad |
P9041
|
FINISHED |
| Object | M3 freeway |
—
|
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: M3 freeway | Statement: [Newlands Forest, accessFromRoad, M3 freeway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessFromRoad Context triple: [Newlands Forest, accessFromRoad, M3 freeway]
-
A.
roadAccessFrom
Indicates that one location can be reached from another via a usable road connection.
-
B.
roadAccessArea
Indicates that an area is designated for or provides access to a road, such as for entry, exit, or connection.
-
C.
hasSeparateAccessRoadFor
Indicates that one entity is served by its own distinct access road that is separate from the access road used by another entity.
-
D.
roadAccessVia
chosen
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
-
E.
hasSeparateAccessRoad
Indicates that an entity is served by its own distinct access road, separate from other routes or shared entrances.
- 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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: May 1, 2026, 1:38 a.m.