Triple
T9091865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kunhar River |
E217905
|
entity |
| Predicate | hasLocalEconomyRole |
P1099
|
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: [Kunhar River, hasLocalEconomyRole, tourism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalEconomyRole Context triple: [Kunhar River, hasLocalEconomyRole, tourism]
-
A.
hasEconomicRole
Indicates that an entity participates in or fulfills a specific function, position, or responsibility within an economic system or activity.
-
B.
hasEconomicActivity
chosen
Indicates that an entity engages in, supports, or is associated with a specific type of economic activity or business operation.
-
C.
hasCityRole
Indicates that an entity holds or is assigned a specific role, function, or status within a particular city.
-
D.
localEconomyImpact
Indicates the effect that an action, event, or entity has on the economic conditions, activities, or performance of a specific local area or community.
-
E.
hasEconomicPosition
Indicates that an entity holds a particular role, status, or standing within an economic system or structure.
- 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_69ca83d8ab5881909d8fddae363b32b1 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc96b18b24819097b525ddad3a85c0 |
completed | April 1, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:14 p.m.