Triple
T25890241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kooyong railway station |
E652309
|
entity |
| Predicate | electrifiedYear |
P59370
|
FINISHED |
| Object | 1922 |
—
|
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: 1922 | Statement: [Kooyong railway station, electrifiedYear, 1922]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electrifiedYear Context triple: [Kooyong railway station, electrifiedYear, 1922]
-
A.
electrificationYear
chosen
Indicates the year in which something (such as a system, facility, or infrastructure) was converted to or equipped for electric power.
-
B.
isElectrifiedSince
Indicates that an entity has had electrical power or electrification continuously from a specified point in time onward.
-
C.
electrificationUsedBetween
Indicates that an electrification system or method is applied or present along the segment or connection between two entities.
-
D.
electrificationStart
Indicates the point in time or event when the process of providing electric power to something begins.
-
E.
emergenceYear
Indicates the calendar year in which something first appeared, originated, or came into existence.
- 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_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 22, 2026, 8:19 a.m.