Triple
T17472143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Adelaide-Enfield |
E425443
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Alberton |
—
|
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: Alberton | Statement: [Port Adelaide-Enfield, contains, Alberton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alberton Context triple: [Port Adelaide-Enfield, contains, Alberton]
-
A.
Alberton
Alberton is a town in the East Rand region of Gauteng, South Africa, forming part of the greater Johannesburg metropolitan area.
-
B.
Alberton
chosen
Alberton is an inner north-western suburb of Adelaide, South Australia, historically known as the traditional home of the Port Adelaide Football Club.
-
C.
Alberton
Alberton is a small rural township located within Ontario’s Rainy River District in Canada.
-
D.
Alloa
Alloa is a town in central Scotland that serves as the main commercial and population hub of Clackmannanshire.
-
E.
Dumbarton
Dumbarton is a historic Scottish town on the River Clyde known for its prominent role in shipbuilding and maritime industry.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451b8a51081908d94bebe2417e3d3 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 5:47 a.m.