Triple
T7488526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Jutland |
E176943
|
entity |
| Predicate | isEconomicallySignificant |
P46888
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [East Jutland, isEconomicallySignificant, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEconomicallySignificant Context triple: [East Jutland, isEconomicallySignificant, true]
-
A.
hasEconomicDimension
chosen
Indicates that something involves, affects, or is characterized by economic factors, considerations, or consequences.
-
B.
isEconomicCenter
Indicates that an entity functions as a primary hub for economic activity, such as trade, finance, or industry, within a region or system.
-
C.
hasEconomicFocus
Indicates that an entity is primarily concerned with, oriented toward, or specializing in economic matters, activities, or impacts.
-
D.
hasEconomyCharacteristic
Indicates that an economy possesses a particular attribute, feature, or quality.
-
E.
hasEconomicInterest
Indicates that one entity stands to gain or lose financially or materially from the performance, decisions, or outcomes associated with another entity.
- 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_69c69f24ac508190bb98fe927c0bd065 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f55965ac81909d3c3a5422b22d44 |
completed | March 27, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c6f03eeaa88190a5215772ed05ee9f |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:43 p.m.