Triple
T554334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hualapai people |
E11908
|
entity |
| Predicate | notableEconomicActivity |
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: [Hualapai people, notableEconomicActivity, tourism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEconomicActivity Context triple: [Hualapai people, notableEconomicActivity, tourism]
-
A.
hasEconomicActivity
chosen
Indicates that an entity engages in, supports, or is associated with a specific type of economic activity or business operation.
-
B.
notableIndustry
Indicates that an entity is significantly recognized or prominent within a specified industry or sector.
-
C.
hasEconomicRole
Indicates that an entity participates in or fulfills a specific function, position, or responsibility within an economic system or activity.
-
D.
economicClassification
Indicates how an entity is categorized based on its economic characteristics, status, or role within an economic system.
-
E.
economyIncludes
Indicates that an economy encompasses, contains, or is composed of the specified component, sector, or element.
- 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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4991c524481908b2bb88c4feabec6 |
completed | March 1, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69a494bc1f8c8190904356f3a8e801de |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.