Triple
T32584964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medway services |
E832895
|
entity |
| Predicate | accessibleFromJunction |
P1985
|
FINISHED |
| Object | M2 Junction 4 |
—
|
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: M2 Junction 4 | Statement: [Medway services, accessibleFromJunction, M2 Junction 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessibleFromJunction Context triple: [Medway services, accessibleFromJunction, M2 Junction 4]
-
A.
accessibleFrom
chosen
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
B.
accessibleFromStation
Indicates that a location or facility can be reached directly or conveniently starting from a given station.
-
C.
hasPedestrianAccessTo
Indicates that a location or area can be reached or entered safely and directly by people on foot.
-
D.
isRoadAccessible
Indicates that a road can be safely and legally used or traversed under the current conditions.
-
E.
hasSeparateAccessRoadFor
Indicates that one entity is served by its own distinct access road that is separate from the access road used by another entity.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: May 1, 2026, 1:04 a.m.