Triple
T7626473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glen Waverley line |
E172645
|
entity |
| Predicate | servesSuburb |
P82
|
FINISHED |
| Object | Willison |
E623246
|
NE 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: Willison | Statement: [Glen Waverley line, servesSuburb, Willison]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Willison Context triple: [Glen Waverley line, servesSuburb, Willison]
-
A.
Willison
chosen
Willison is a small suburban railway station in Melbourne, Australia, located on the Alamein line and serving the surrounding residential area.
-
B.
Wilkin
Wilkin is a medieval English given name that originated as a diminutive form of William and later gave rise to the surname Wilkinson.
-
C.
Willson
Willson is a less common spelling variant of the surname Wilson, typically used as a family name or occasionally as a given name.
-
D.
Wilsen
Wilsen is a variant form of the given name Wilson, used as a personal name or surname.
-
E.
Weeley
Weeley is a small village and civil parish in the Tendring district of Essex, England, known for its rural character and proximity to the Essex coast.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c699517e348190bd3348b6889200f2 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fa8150ac8190908aec411b0f4e50 |
completed | March 27, 2026, 9:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c870a518f48190a4bba3657a7844f4 |
completed | March 29, 2026, 12:21 a.m. |
Created at: March 27, 2026, 3:56 p.m.