Triple
T24814623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglican Province of Queensland |
E620882
|
entity |
| Predicate | hasProvinceWithin |
P98125
|
FINISHED |
| Object | Australia |
—
|
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: Australia | Statement: [Anglican Province of Queensland, hasProvinceWithin, Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProvinceWithin Context triple: [Anglican Province of Queensland, hasProvinceWithin, Australia]
-
A.
hasProvinceOrRegion
chosen
Indicates that one entity includes, is associated with, or is located within a specific province or region as an administrative or geographic subdivision.
-
B.
hasProvinceType
Indicates that an entity is associated with a province classified by a specific type or category.
-
C.
hasProvincialCapitalWithin
Indicates that a province’s official capital city is geographically located within the boundaries of a specified area or region.
-
D.
hasNearbyProvince
Indicates that one province is geographically close to or directly adjacent to another province.
-
E.
isInProvince
Indicates that one entity (typically a place or city) is located within the administrative boundaries of a specified province.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 18, 2026, 5:01 a.m.