Triple
T32781531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R27 |
E838366
|
entity |
| Predicate | hasPlatformGroup |
P191814
|
FINISHED |
| Object | Broad Street station platforms |
—
|
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: Broad Street station platforms | Statement: [R27, hasPlatformGroup, Broad Street station platforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlatformGroup Context triple: [R27, hasPlatformGroup, Broad Street station platforms]
-
A.
hasStationGroup
Indicates that an entity is associated with, or belongs to, a particular group or collection of stations.
-
B.
hasSiteGroup
Indicates that an entity is associated with or belongs to a particular site group.
-
C.
hasCentralGroup
Indicates that an entity possesses or is associated with a primary or central group within its structure or organization.
-
D.
hasUserGroup
Indicates that a user is associated with, belongs to, or is a member of a specific user group.
-
E.
hasCorporateGroup
Indicates that one corporate entity belongs to, or is associated with, a broader corporate group or conglomerate.
- 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
| PDg | Predicate description generation | batch_69fcec5e560481909cd710b88897e833 |
completed | May 7, 2026, 7:47 p.m. |
Created at: May 1, 2026, 1:14 a.m.