Triple
T23691720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Province of Australia |
E585317
|
entity |
| Predicate | hasMetropolitanStructure |
P153424
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
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: true | Statement: [Province of Australia, hasMetropolitanStructure, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMetropolitanStructure Context triple: [Province of Australia, hasMetropolitanStructure, true]
-
A.
hasMetropolitan
Indicates that an entity is associated with, served by, or located within a specific metropolitan area.
-
B.
isMetropolitanFor
Indicates that one entity serves as the primary metropolitan center or urban hub for another entity (such as a region, area, or service).
-
C.
hasMetropolitanSee
Indicates that one ecclesiastical jurisdiction serves as the metropolitan (primary or overseeing) see in relation to another church territory.
-
D.
hasMetropolitanRankOver
Indicates that one entity has a higher metropolitan rank or status than another entity.
-
E.
hasMetropolitanCityCapital
Indicates that an administrative region or entity has, as its capital, a city classified as a metropolitan city.
- 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_69e249037ce0819088b149608e98f685 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b5c27af481908c6dbe59c71de82a |
completed | April 29, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f157cc43a881909ed2d8b0a09b5d73 |
completed | April 29, 2026, 12:58 a.m. |
Created at: April 17, 2026, 6:52 p.m.