Triple
T26240941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adelaide–Melbourne railway |
E656310
|
entity |
| Predicate | connectsStateOrTerritory |
P115309
|
FINISHED |
| Object | South Australia |
—
|
NE NERFINISHED |
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: South Australia | Statement: [Adelaide–Melbourne railway, connectsStateOrTerritory, South Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsStateOrTerritory Context triple: [Adelaide–Melbourne railway, connectsStateOrTerritory, South Australia]
-
A.
connectsStates
chosen
Indicates a relationship where one entity serves as a link or route that joins two or more states together.
-
B.
connectsProvinceOrRegion
Indicates that one entity serves to link or provide a connection between a specific province or region and another entity.
-
C.
startStateOrTerritory
Indicates the state or territory in which an event, process, or relationship begins or is initially situated.
-
D.
stateOrTerritory
Indicates that one entity is a state or territory that is politically or administratively associated with another entity.
-
E.
borderingStateOrTerritory
Indicates that one state or territory shares a common boundary with another state or territory.
- 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_69ee5b4c59a881909d9ee4fd013fffd5 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 26, 2026, 9:03 p.m.