Triple
T25704009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balnibarbi |
E644537
|
entity |
| Predicate | economyStatus |
P161660
|
FINISHED |
| Object | impoverished |
—
|
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: impoverished | Statement: [Balnibarbi, economyStatus, impoverished]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: economyStatus Context triple: [Balnibarbi, economyStatus, impoverished]
-
A.
economicPolicyStatus
Indicates the current condition or stance of an entity’s economic policies, such as whether they are active, proposed, suspended, or otherwise characterized.
-
B.
economyIncludes
Indicates that an economy encompasses, contains, or is composed of the specified component, sector, or element.
-
C.
economicFunction
Indicates the role or purpose an entity serves within an economic system, such as how it contributes to production, distribution, or consumption of goods and services.
-
D.
economicTrend
Indicates the general direction or pattern of economic activity or conditions over a period of time.
-
E.
economyContrast
Indicates that two entities are being compared or opposed in terms of their economic characteristics, conditions, or performance.
- F. None of above. chosen
Provenance (4 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6200ac60481909895c61d050b1338 |
completed | May 2, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61f109ef48190873bfe18638d2046 |
completed | May 2, 2026, 3:58 p.m. |
Created at: April 21, 2026, 9 p.m.