Triple
T1107666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nordic |
E25522
|
entity |
| Predicate | usesRegionalCooperationLabel |
P19377
|
FINISHED |
| Object | Nordic cooperation |
—
|
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: Nordic cooperation | Statement: [Nordic, usesRegionalCooperationLabel, Nordic cooperation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRegionalCooperationLabel Context triple: [Nordic, usesRegionalCooperationLabel, Nordic cooperation]
-
A.
regionalBloc
Indicates that an entity is a member of, or associated with, a specific regional political or economic bloc.
-
B.
cooperatingState
chosen
Indicates that one state collaborates or works jointly with another state toward shared goals or activities.
-
C.
involvedInternationalOrganization
Indicates that an entity participates in, is affiliated with, or plays a role within an international organization.
-
D.
hasRegionalCommission
Indicates that an entity is associated with, overseen by, or falls under the jurisdiction of a specific regional commission.
-
E.
countryPartner
Indicates a formal partnership relationship between two countries, such as cooperation, alliance, or strategic collaboration.
- 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9e47e4881908928900df72781f0 |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b749e2a881909ef28745a7d2d917 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:43 p.m.