Triple
T35176521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balmain Tigers |
E1015718
|
entity |
| Predicate | traditionalHomeGroundSuburb |
P47577
|
FINISHED |
| Object | Leichhardt |
—
|
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: Leichhardt | Statement: [Balmain Tigers, traditionalHomeGroundSuburb, Leichhardt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalHomeGroundSuburb Context triple: [Balmain Tigers, traditionalHomeGroundSuburb, Leichhardt]
-
A.
suburb
chosen
Indicates that one place is a residential district or outlying area that is part of or adjacent to a larger city or town.
-
B.
traditionalHousingRegion
Indicates the region where a group’s customary or historically established housing patterns are typically found.
-
C.
traditionalHomeEnd
Indicates the point or time at which a traditional home, household, or customary domestic arrangement comes to an end.
-
D.
realWorldSuburb
Indicates that one entity is a suburb that exists in the real world, as opposed to a fictional or abstract suburb.
-
E.
isResidentialSuburbOf
Indicates that one area is a residential suburb that is part of or lies within the urban region of another area.
- 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_69f76ddcc108819097f96853b7ed9ef4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff5285ed74819097e6e2a9084a079a |
completed | May 9, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69ff51fbe28881908ac8417dff9db81a |
completed | May 9, 2026, 3:25 p.m. |
Created at: May 3, 2026, 4:02 p.m.