Triple
T23804754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglican Bishop of Canberra and Goulburn |
E589672
|
entity |
| Predicate | primaryCityInTitle |
P136244
|
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: [Anglican Bishop of Canberra and Goulburn, primaryCityInTitle, Canberra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCityInTitle Context triple: [Anglican Bishop of Canberra and Goulburn, primaryCityInTitle, Canberra]
-
A.
primaryCity
Indicates that one city serves as the main or most important city associated with a given region, entity, or context.
-
B.
principalCityOf
Indicates that a city serves as the main or most important city (often administrative, economic, or cultural center) of a specified region or area.
-
C.
primaryCityDocumented
Indicates that a city is recorded or designated as the main or principal city associated with a given entity or context.
-
D.
primaryLocationCity
chosen
Indicates the city that serves as the main or primary location associated with the subject.
-
E.
primaryTown
Indicates that a given town is the main or most important town associated with an entity (such as a person, organization, or region).
- 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_69e25d19fecc8190a5cf39bbb18d5d7f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7511db08190aa3eb08f3e3ae515 |
completed | April 29, 2026, 8:54 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:55 p.m.