Triple
T27568925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTA Red Line |
E695976
|
entity |
| Predicate | primaryDowntownHub |
P26184
|
FINISHED |
| Object | Tower City–Public Square station |
E764039
|
NE 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: Tower City–Public Square station | Statement: [RTA Red Line, primaryDowntownHub, Tower City–Public Square station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryDowntownHub Context triple: [RTA Red Line, primaryDowntownHub, Tower City–Public Square station]
-
A.
isDowntownHub
Indicates that a location functions as a central, primary hub within a city’s downtown area.
-
B.
primaryHubFor
Indicates that one entity serves as the main central hub or core point of coordination for another entity or set of entities.
-
C.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
-
D.
connectsDowntownTo
chosen
Indicates a relationship where one location, route, or service provides a direct connection or access to a downtown area.
-
E.
isDowntownEndpointOf
Indicates that a location serves as the downtown terminus or endpoint of a route, line, or path.
- F. None of above.
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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69ff59b33a38819086cc9aa19b81748b |
completed | May 9, 2026, 3:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a12da7bb3c88190ba2a7d2590a13a50 |
completed | May 24, 2026, 11:01 a.m. |
| PD | Predicate disambiguation | batch_69ff587758f88190a39c2164341dc554 |
completed | May 9, 2026, 3:53 p.m. |
Created at: April 27, 2026, 1:42 p.m.