Triple
T12695922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coolgardie |
E303331
|
entity |
| Predicate | economicBaseToday |
P12253
|
FINISHED |
| Object | tourism |
—
|
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: tourism | Statement: [Coolgardie, economicBaseToday, tourism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: economicBaseToday Context triple: [Coolgardie, economicBaseToday, tourism]
-
A.
economicView
Indicates a relationship where one entity holds or expresses a particular economic belief, stance, or perspective regarding economic systems, policies, or issues.
-
B.
economicTrend
Indicates the general direction or pattern of economic activity or conditions over a period of time.
-
C.
economicFunction
chosen
Indicates the role or purpose an entity serves within an economic system, such as how it contributes to production, distribution, or consumption of goods and services.
-
D.
economyIncludes
Indicates that an economy encompasses, contains, or is composed of the specified component, sector, or element.
-
E.
economicDataSource
Indicates the source or origin from which economic data or statistics are obtained or derived.
- 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d962a32c6481908ddaddae4ea267bf |
completed | April 10, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69d960be63f081908a5ef5ef17a311bf |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:22 p.m.