Triple
T10895544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karratha |
E257298
|
entity |
| Predicate | isMiningHub |
P19172
|
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: [Karratha, isMiningHub, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMiningHub Context triple: [Karratha, isMiningHub, true]
-
A.
hasMiningActivity
chosen
Indicates that some form of mining operation or extraction activity is occurring at, involving, or associated with the referenced entity.
-
B.
isITHubOf
Indicates that an entity serves as a central location or primary center for IT-related activities, services, or operations for another entity or area.
-
C.
isCommercialHubIn
Indicates that a place functions as a primary center of commercial or business activity within a specified larger area or region.
-
D.
isBusyHub
Indicates that a location or node functions as a central point of activity with a high volume of interactions, traffic, or connections.
-
E.
isSmallHub
Indicates that an entity functions as a hub of relatively limited size, capacity, or connectivity within a larger network or system.
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75d022f4c81909cd9ea27a9f0cd32 |
completed | April 9, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.