Triple
T28279206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stourbridge Junction |
E713092
|
entity |
| Predicate | hasBranchTo |
P98302
|
FINISHED |
| Object | Stourbridge Town |
—
|
NE NERFINISHED |
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: Stourbridge Town | Statement: [Stourbridge Junction, hasBranchTo, Stourbridge Town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBranchTo Context triple: [Stourbridge Junction, hasBranchTo, Stourbridge Town]
-
A.
hasBranches
chosen
Indicates that an entity extends into multiple subordinate parts or offshoots, like limbs, divisions, or sections stemming from a main source.
-
B.
hasBranchName
Indicates that an entity (such as a branch or subdivision) bears or is identified by a specific branch name.
-
C.
hasBranchRole
Indicates that an entity holds or is assigned a specific role or position within a particular branch or subdivision of an organization.
-
D.
hadBranchIn
Indicates that an organization or entity maintained a branch, office, or subsidiary located in another specified place or entity.
-
E.
mayHaveBranch
Indicates that an entity is permitted or able to possess one or more branches as part of its structure or organization.
- 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_69efb52275788190ae5181ccebef18ce |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 27, 2026, 11:21 p.m.