Triple
T36809146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murwillumbah railway station |
E909539
|
entity |
| Predicate | closingDateForRegularServices |
P176633
|
FINISHED |
| Object | 16 May 2004 |
—
|
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: 16 May 2004 | Statement: [Murwillumbah railway station, closingDateForRegularServices, 16 May 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closingDateForRegularServices Context triple: [Murwillumbah railway station, closingDateForRegularServices, 16 May 2004]
-
A.
closureDateForRegularService
chosen
Indicates the date on which a regular, ongoing service is formally closed or terminated.
-
B.
closingTime
Indicates the specific time at which a place, service, or activity stops operating or becomes unavailable.
-
C.
closureTime
Indicates the time at which an entity, event, or process is formally closed, ended, or no longer available.
-
D.
closingLocation
Indicates the place or venue where an event, process, or activity comes to an end or is formally concluded.
-
E.
closedOnDate
Indicates that an entity ceases or ceased operations or availability on a specific calendar date.
- 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_69f76e7cbbf48190891227b14d041139 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7ca93bd0481909d6eee9e950001a1 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:13 p.m.