Triple
T28257607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nordic Green Left |
E712492
|
entity |
| Predicate | memberPartyRegion |
P99768
|
FINISHED |
| Object | Denmark |
—
|
NE NERFINISHED |
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: [Nordic Green Left, memberPartyRegion, Denmark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberPartyRegion Context triple: [Nordic Green Left, memberPartyRegion, Denmark]
-
A.
hasRegionalParty
Indicates that an entity is associated with or represented by a political party that operates at a regional or subnational level.
-
B.
partyBaseRegion
chosen
Indicates the geographic region that serves as the primary base or stronghold for a political party.
-
C.
politicalRegionRepresented
Indicates that one entity serves as the official political representative or governing body for a specified geographic or administrative region.
-
D.
participantsRegion
Indicates that the related entities are associated with, originate from, or operate within a specified geographic region.
-
E.
subRegionalMembership
Indicates that an entity belongs to or is a member of a specific subregional grouping within a larger region or organization.
- 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_69efb5207eb08190827e4c34048030b1 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 27, 2026, 11:09 p.m.