Triple
T33041716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strensham services |
E845483
|
entity |
| Predicate | hasCashMachine |
P41921
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Strensham services, hasCashMachine, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCashMachine Context triple: [Strensham services, hasCashMachine, yes]
-
A.
hasATMNetwork
chosen
Indicates that an entity operates, participates in, or is connected to a particular automated teller machine (ATM) network for financial transactions.
-
B.
hasCashForm
Indicates that something exists or is available specifically in the form of cash.
-
C.
hasCashWraps
Indicates that an entity is equipped with one or more cash wrap areas or checkout counters for handling customer transactions.
-
D.
hasOpalTopUpMachine
Indicates that a location or facility is equipped with an Opal card top-up machine for adding credit or purchasing travel value.
-
E.
hasBankOn
Indicates that one entity is located on or alongside the bank (edge) of another entity, typically a river, lake, or similar body.
- 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_69f34951348c8190b56746b0a7018182 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff136ed2a881908f713401083970d1 |
completed | May 9, 2026, 10:58 a.m. |
| PD | Predicate disambiguation | batch_69ff10f9e3448190b6cb6ea5a67713c1 |
completed | May 9, 2026, 10:48 a.m. |
Created at: May 1, 2026, 1:24 a.m.