Triple
T13704491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Park Street station |
E328604
|
entity |
| Predicate | hasSubwayLevel |
P89525
|
FINISHED |
| Object | Green Line level |
—
|
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: Green Line level | Statement: [Park Street station, hasSubwayLevel, Green Line level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubwayLevel Context triple: [Park Street station, hasSubwayLevel, Green Line level]
-
A.
hasUndergroundLevel
Indicates that one entity possesses or includes a level, floor, or section that is located below ground level.
-
B.
hasSubway
Indicates that a place is served by or contains a subway (metro) system.
-
C.
hasSubwayComplex
Indicates that one entity contains or is associated with a subway complex as part of its structure or facilities.
-
D.
hasUndergroundSection
Indicates that an entity includes a portion or segment that is located below ground level.
-
E.
hasSubwayPlatforms
chosen
Indicates that an entity is equipped with one or more platforms specifically serving a subway or metro rail system.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dcad17732c8190bbd0d73107711c99 |
completed | April 13, 2026, 8:45 a.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:54 p.m.