Triple
T25423153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kambah |
E637037
|
entity |
| Predicate | isLargestSuburbOf |
P158490
|
FINISHED |
| Object | Canberra |
—
|
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: Canberra | Statement: [Kambah, isLargestSuburbOf, Canberra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLargestSuburbOf Context triple: [Kambah, isLargestSuburbOf, Canberra]
-
A.
isLargestTownOn
Indicates that one town is the largest (by size, population, or another defined measure) among all towns located on a specified geographic feature or area.
-
B.
isEasternSuburbOf
Indicates that one place is a suburb located to the east of another place.
-
C.
nearestLargeSuburb
Indicates that one location is the closest nearby suburb that is considered large relative to other surrounding suburbs.
-
D.
isOuterSuburbOf
Indicates that one place is a suburban area located on the outer edge or periphery of another, typically larger, urban area.
-
E.
largestCityOnItsEdge
Indicates that one city is the largest (by some measure, typically population) among all cities located on the boundary or edge of a given region or area.
- F. None of above. chosen
Provenance (4 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6be79b0819093a406e1f9b1348c |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 1:57 p.m.