Triple
T25476693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Essendon Football Club |
E638451
|
entity |
| Predicate | historicalSuburb |
P165283
|
FINISHED |
| Object | Essendon |
—
|
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: Essendon | Statement: [Essendon Football Club, historicalSuburb, Essendon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalSuburb Context triple: [Essendon Football Club, historicalSuburb, Essendon]
-
A.
isHistoricSuburbOf
chosen
Indicates that one suburb has historical significance and is recognized as part of, or historically associated with, a larger city or town.
-
B.
historicalLocalGovernmentArea
Indicates that an entity was once administered as a local government area in the past but no longer holds that status.
-
C.
originalSuburbBase
Indicates that one location serves as the original or primary suburban area from which another related suburb or suburban entity is derived or defined.
-
D.
isEasternSuburbOf
Indicates that one place is a suburb located to the east of another place.
-
E.
isCommercialSuburbOf
Indicates that one area functions primarily as a business or commercial district that is part of, or subordinate to, a larger urban area or city.
- 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 21, 2026, 2:26 p.m.