Triple
T24396281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acle Straight |
E615034
|
entity |
| Predicate | hasEndpointNear |
P118122
|
FINISHED |
| Object | Great Yarmouth outskirts |
—
|
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: Great Yarmouth outskirts | Statement: [Acle Straight, hasEndpointNear, Great Yarmouth outskirts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndpointNear Context triple: [Acle Straight, hasEndpointNear, Great Yarmouth outskirts]
-
A.
hasNearbyPoint
chosen
Indicates that one entity has at least one other point located within a specified proximity or distance from it.
-
B.
hasEndpointStation
Indicates that something (such as a route, line, or service) has a specific station as one of its terminal endpoints.
-
C.
hasNearbyFunction
Indicates that one entity has another entity located close by that serves a related or supportive function.
-
D.
hasNearbyCrossingPoint
Indicates that one location has a crossing point (such as a bridge, crosswalk, or intersection) situated close to it.
-
E.
hasNearbyMode
Indicates that one entity has another entity located close enough to be considered in its immediate vicinity or surrounding area.
- 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_69e2d7e509b88190a53155d4f3de45ce |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f294d79dac8190bb79519f4aed91f2 |
completed | April 29, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:04 a.m.