Triple
T9702963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GCM |
E234822
|
entity |
| Predicate | connectedToSubwayLines |
P17559
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [GCM, connectedToSubwayLines, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToSubwayLines Context triple: [GCM, connectedToSubwayLines, 4]
-
A.
subwayLine
Indicates that there is a subway line connection or service relationship between the referenced entities.
-
B.
hasSubwayLineAboveOrBelow
Indicates that one subway line is physically located above or below another subway line, such as on different levels of a transit system.
-
C.
hasMetroLine
chosen
Indicates that a location or area is served by, or connected to, a specific metro (subway) line.
-
D.
monorailLines
Indicates that there is a monorail transit line or system associated with, serving, or present in the referenced entity.
-
E.
hasUndergroundConnections
Indicates that one entity is linked to another through subterranean or hidden passageways, networks, or channels.
- 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_69ca84cc78808190a56f3402b7c139a7 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d73a0148190ad4178fd462cdd9c |
completed | April 1, 2026, 10:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03b641408190942464eaf174c6b5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:18 p.m.