Triple
T30992773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltic Sea region |
E789711
|
entity |
| Predicate | hasCoreMemberCountry |
P20032
|
FINISHED |
| Object | Denmark |
E5474
|
NE 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: Denmark | Statement: [Baltic Sea region, hasCoreMemberCountry, Denmark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreMemberCountry Context triple: [Baltic Sea region, hasCoreMemberCountry, Denmark]
-
A.
hasCoreMember
chosen
Indicates that an entity includes another entity as a central or primary member of its group, organization, or structure.
-
B.
hasMemberNation
Indicates that a particular nation belongs to or is included as a member within a larger group, organization, or union.
-
C.
hasNonRegionalMemberCountries
Indicates that an organization includes member countries that are not part of the primary geographic region with which the organization is associated.
-
D.
hasContributingCountry
Indicates that a country has contributed resources, support, or participation to the subject entity or activity.
-
E.
hasOriginalMemberNation
Indicates that an entity was among the founding or initial member nations of another entity, such as an organization or alliance.
- F. None of above.
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_69f224c65a348190baaed1c01a29900c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a01b841f5508190832bba00cf795bad |
completed | May 11, 2026, 11:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a292af8ef4c8190928576822e52853f |
completed | June 10, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_6a01b59541fc8190a9b13a55327c4aa1 |
completed | May 11, 2026, 10:55 a.m. |
Created at: April 29, 2026, 8:56 p.m.