Triple

T25393775
Position Surface form Disambiguated ID Type / Status
Subject Murrumbeena railway station E636235 entity
Predicate rebuiltAsElevated P84662 FINISHED
Object 2018 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: 2018 | Statement: [Murrumbeena railway station, rebuiltAsElevated, 2018]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: rebuiltAsElevated
Context triple: [Murrumbeena railway station, rebuiltAsElevated, 2018]
  • A. reconstructedAsElevated chosen
    Indicates that something has been rebuilt, modeled, or interpreted as having a higher or raised position relative to its original or surrounding context.
  • B. rebuiltUnder
    Indicates that an entity was reconstructed or restored while being subject to the authority, control, or governance of another entity.
  • C. rebuiltFor
    Indicates that one entity has been reconstructed, renovated, or modified specifically to serve the needs, purposes, or use of another entity.
  • D. laterRebuiltAs
    Indicates that one entity was reconstructed or redeveloped at a later time to become or be replaced by another specific entity.
  • E. rebuild
    Indicates restoring or constructing again something that was previously built, often after damage, destruction, or significant alteration.
  • 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_69e75db263888190b77fff9e2827b9a2 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f56572b9288190abaf921c761fd843 completed May 2, 2026, 2:46 a.m.
PD Predicate disambiguation batch_69f4806d93dc8190b9dff4c63186faff completed May 1, 2026, 10:29 a.m.
Created at: April 21, 2026, 1:49 p.m.