Triple
T16322282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redcliffe Way |
E396325
|
entity |
| Predicate | hasRoleInArea |
P96909
|
FINISHED |
| Object | connects parts of Redcliffe area |
—
|
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: connects parts of Redcliffe area | Statement: [Redcliffe Way, hasRoleInArea, connects parts of Redcliffe area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoleInArea Context triple: [Redcliffe Way, hasRoleInArea, connects parts of Redcliffe area]
-
A.
isInArea
Indicates that one entity is located within the spatial bounds or region defined by another entity.
-
B.
hasProtectedAreaAccess
Indicates that an entity is permitted to enter, use, or otherwise access a designated protected area under defined conditions.
-
C.
hasNeighborhoodRole
chosen
Indicates that an entity holds a specific role, function, or position within a neighborhood or local community context.
-
D.
hasAreaType
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
-
E.
hasRegionalRole
Indicates that an entity holds a specific role, function, or responsibility within a defined geographic region.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e296b706108190b43a05b784633050 |
completed | April 17, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.