Triple
T10762941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appalachian Ohio |
E253877
|
entity |
| Predicate | historicalEconomyType |
P10778
|
FINISHED |
| Object | rural |
—
|
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: rural | Statement: [Appalachian Ohio, historicalEconomyType, rural]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalEconomyType Context triple: [Appalachian Ohio, historicalEconomyType, rural]
-
A.
historicalEconomicBase
chosen
Indicates the primary type of economic activity or production that historically underpinned or sustained an entity’s economy.
-
B.
historicalType
Indicates that one entity classifies or characterizes another in terms of its role, status, or category within a historical context.
-
C.
historicalCategory
Indicates that an entity is classified within a particular historical grouping, period, or type based on its time-related characteristics or context.
-
D.
regionalEconomyType
Indicates the type or classification of an economy associated with a specific region.
-
E.
historicalBase
Indicates that one entity serves as the original or foundational source, model, or precedent upon which the other entity is historically based.
- 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d731a373708190ae5ac0c027a4014c |
completed | April 9, 2026, 4:57 a.m. |
| PD | Predicate disambiguation | batch_69d6f311529c819080ca5493d55d6050 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:16 p.m.