Triple
T14731844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurstville railway station |
E346093
|
entity |
| Predicate | rebuildOrMajorUpgrade |
P41357
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [Hurstville railway station, rebuildOrMajorUpgrade, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebuildOrMajorUpgrade Context triple: [Hurstville railway station, rebuildOrMajorUpgrade, 1990s]
-
A.
majorRebuilder
Indicates that an entity plays a primary or leading role in reconstructing, restoring, or significantly rebuilding another entity.
-
B.
isMajorUpgrade
Indicates that one version or change represents a significant, non-trivial upgrade over another in terms of scope, impact, or functionality.
-
C.
majorRebuildCompleted
Indicates that a significant reconstruction or overhaul of an entity has been fully completed.
-
D.
rebuild
chosen
Indicates restoring or constructing again something that was previously built, often after damage, destruction, or significant alteration.
-
E.
majorRevision
Indicates a substantial change or overhaul made to something, significantly altering its previous form or content.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec26311c8819093a81ff0fa43b33b |
completed | April 14, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:29 a.m.