Triple
T31727158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sari, Georgia |
E809756
|
entity |
| Predicate | likelyPrimaryEconomicCharacter |
P32182
|
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: [Sari, Georgia, likelyPrimaryEconomicCharacter, rural]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyPrimaryEconomicCharacter Context triple: [Sari, Georgia, likelyPrimaryEconomicCharacter, rural]
-
A.
hasEconomyCharacteristic
Indicates that an economy possesses a particular attribute, feature, or quality.
-
B.
primaryEconomicHinterland
Indicates that one place serves as the main surrounding area that economically supports, supplies, or is influenced by another place.
-
C.
economicExtensionOf
Indicates that one entity’s economy is heavily dependent on, controlled by, or functions as an outgrowth of another entity’s economic system.
-
D.
hasEconomicRole
Indicates that an entity participates in or fulfills a specific function, position, or responsibility within an economic system or activity.
-
E.
regionalEconomyType
chosen
Indicates the type or classification of an economy associated with a specific region.
- 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_69f348e009c8819095d77df52c645b9c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 30, 2026, 11:20 p.m.