Triple
T31883094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stourbridge Town |
E813932
|
entity |
| Predicate | hasShortBranchLine |
P180266
|
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: [Stourbridge Town, hasShortBranchLine, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShortBranchLine Context triple: [Stourbridge Town, hasShortBranchLine, yes]
-
A.
isShortLine
Indicates that a line is relatively short in length compared to a standard or other lines.
-
B.
hasBranchLinePurpose
Indicates that a branch line is associated with a specific intended function or purpose within a larger network or system.
-
C.
isOnShortLine
Indicates that one entity is positioned on or along a line segment that is classified as short relative to other lines in the context.
-
D.
hasShort
Indicates that an entity possesses or is characterized by something of short length or duration.
-
E.
branchLine
Indicates a relationship where one line, route, or path diverges from and is subordinate to a main or primary line.
- F. None of above. chosen
Provenance (4 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
| PDg | Predicate description generation | batch_69f739a58b3c81908abc2b8738a65678 |
completed | May 3, 2026, 12:03 p.m. |
Created at: April 30, 2026, 11:56 p.m.