Triple
T10602765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leigh Delamere services |
E275790
|
entity |
| Predicate | hasDirectionSpecificSite |
P61247
|
FINISHED |
| Object | Leigh Delamere services eastbound |
—
|
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: Leigh Delamere services eastbound | Statement: [Leigh Delamere services, hasDirectionSpecificSite, Leigh Delamere services eastbound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectionSpecificSite Context triple: [Leigh Delamere services, hasDirectionSpecificSite, Leigh Delamere services eastbound]
-
A.
isSiteSpecific
Indicates that something is designed, intended, or valid only for a particular location, context, or site and does not generally apply elsewhere.
-
B.
hasDirectionVariant
chosen
Indicates that one entity is a directional variant or orientation-specific form of another entity.
-
C.
hasDirectionScheme
Indicates that an entity is associated with or governed by a particular scheme or system for defining directions.
-
D.
hasDirectionType
Indicates that something possesses or is associated with a specific type or category of direction.
-
E.
containsSite
Indicates that one entity spatially or structurally includes another entity as a site or location within its bounds.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df4992248190b640d743ccf02c82 |
completed | April 8, 2026, 11:05 p.m. |
| PD | Predicate disambiguation | batch_69d6dd72c1288190adbb5e79e94c044a |
completed | April 8, 2026, 10:57 p.m. |
Created at: April 8, 2026, 7:31 p.m.