Triple
T11676635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shire of Broome |
E277508
|
entity |
| Predicate | isRemoteArea |
P82832
|
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: [Shire of Broome, isRemoteArea, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRemoteArea Context triple: [Shire of Broome, isRemoteArea, true]
-
A.
isInRemoteArea
chosen
Indicates that an entity is located in a geographically isolated or sparsely populated area, typically far from urban centers or standard infrastructure.
-
B.
isRemoteCommunity
Indicates that a community is geographically isolated or distant from urban centers and services.
-
C.
isRemoteOutpostFor
Indicates that one location functions as a distant, often isolated operational base or support site for another primary location or organization.
-
D.
isInArea
Indicates that one entity is located within the spatial bounds or region defined by another entity.
-
E.
isRemoteByRoad
Indicates that one location is difficult or time-consuming to reach from another when traveling by road.
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a46000a48190888ad1a6ade052e3 |
completed | April 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69d88a77e6e88190b7519100bde76575 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.