Triple
T8306476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Spey |
E194474
|
entity |
| Predicate | hasEconomicImportanceIn |
P14281
|
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: [River Spey, hasEconomicImportanceIn, tourism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEconomicImportanceIn Context triple: [River Spey, hasEconomicImportanceIn, tourism]
-
A.
hasEconomicImportanceFor
chosen
Indicates that one entity holds economic value, benefit, or significance for another entity.
-
B.
hasCommercialImportance
Indicates that something possesses economic or business value significant enough to impact trade, revenue, or market activity.
-
C.
hasMainEconomicUse
Indicates that something serves as the primary or principal economic function, purpose, or use of another entity.
-
D.
hasIndustrialSignificance
Indicates that something plays an important role or has notable impact within industrial processes, production, or applications.
-
E.
notableSpeciesRole
Indicates that a species plays a particularly important, characteristic, or influential role in relation to another entity or context.
- 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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f293db08190912e5e8bb7e940cf |
completed | March 31, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:54 p.m.