Triple
T25783792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toorak railway station |
E649361
|
entity |
| Predicate | hasSubwayOrUnderpass |
P173195
|
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: [Toorak railway station, hasSubwayOrUnderpass, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubwayOrUnderpass Context triple: [Toorak railway station, hasSubwayOrUnderpass, yes]
-
A.
hasSubway
Indicates that a place is served by or contains a subway (metro) system.
-
B.
hasOverpassOrSubway
Indicates that one location is connected to or accessible from another via an overpass or a subway passage.
-
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.
hasUndergroundConnections
Indicates that one entity is linked to another through subterranean or hidden passageways, networks, or channels.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 22, 2026, 5:52 a.m.