Triple
T25890244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kooyong railway station |
E652309
|
entity |
| Predicate | hasUndercoverWaitingArea |
P3382
|
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: [Kooyong railway station, hasUndercoverWaitingArea, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUndercoverWaitingArea Context triple: [Kooyong railway station, hasUndercoverWaitingArea, yes]
-
A.
hasWaitingArea
chosen
Indicates that an entity provides or includes a designated space where people can wait before receiving a service or proceeding to another area.
-
B.
hasSecretArea
Indicates that an entity contains or is associated with a hidden or restricted area not normally accessible or visible.
-
C.
hasTicketCollectorArea
Indicates that a location or facility includes a designated area where ticket collectors operate or perform their duties.
-
D.
hasReservationArea
Indicates that an entity is assigned or associated with a specific reserved area or section designated for its use.
-
E.
hasProtectedAreaAccess
Indicates that an entity is permitted to enter, use, or otherwise access a designated protected area under defined conditions.
- 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_69e7ab3b92cc81908febd90317862647 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 22, 2026, 8:19 a.m.