Triple
T19230105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vineta |
E480845
|
entity |
| Predicate | economicRoleInLegend |
P134527
|
FINISHED |
| Object | major Baltic emporium |
—
|
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: major Baltic emporium | Statement: [Vineta, economicRoleInLegend, major Baltic emporium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: economicRoleInLegend Context triple: [Vineta, economicRoleInLegend, major Baltic emporium]
-
A.
inLegendRole
chosen
Indicates that an entity appears in a legendary or mythic context fulfilling a specific narrative or symbolic role.
-
B.
socioeconomicRole
Indicates the social and economic position, function, or status an entity holds within a society or system.
-
C.
positionOnGovernmentRoleInEconomy
Indicates a stance or viewpoint regarding how much and in what ways the government should intervene or participate in the economy.
-
D.
hasEconomicRole
Indicates that an entity participates in or fulfills a specific function, position, or responsibility within an economic system or activity.
-
E.
roleOfPeopleOnIt
Indicates the specific roles or functions that people have in relation to a particular object, event, or context.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa9be0d08190afe6040e0cf9c737 |
completed | April 20, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:25 p.m.