Triple
T33041733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strensham services |
E845483
|
entity |
| Predicate | hasInformationPoint |
P3793
|
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, hasInformationPoint, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInformationPoint Context triple: [Strensham services, hasInformationPoint, yes]
-
A.
hasInformationCentre
Indicates that one entity possesses, hosts, or is served by an information centre associated with it.
-
B.
hasHelpPoint
chosen
Indicates that one entity provides or contains a designated help or assistance point for another entity.
-
C.
hasInformationCenterFor
Indicates that one entity serves as an information center dedicated to providing information or services related to another entity.
-
D.
hasTrailAccessPoint
Indicates that there is a specific access point or entrance connecting a location to a trail or pathway.
-
E.
providesInformationIn
Indicates that one entity supplies or conveys information within or through another entity or context.
- 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_69ffc605b0648190a7abe9128b0d857a |
completed | May 9, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69ffc5742d80819099f947ece78d5700 |
completed | May 9, 2026, 11:38 p.m. |
Created at: May 1, 2026, 1:24 a.m.