Triple
T30930691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kontor of Bruges |
E787984
|
entity |
| Predicate | mainCounterpartRegions |
P26128
|
FINISHED |
| Object | Baltic Sea region |
—
|
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: Baltic Sea region | Statement: [Kontor of Bruges, mainCounterpartRegions, Baltic Sea region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCounterpartRegions Context triple: [Kontor of Bruges, mainCounterpartRegions, Baltic Sea region]
-
A.
mainTradingPartnerRegion
chosen
Indicates the geographic region that serves as the primary trading partner for a given entity.
-
B.
tradePartnerRegion
Indicates that one entity engages in trade with partners located in a specified geographic region.
-
C.
hasCounterpartName
Indicates that an entity has an alternative or corresponding name used as its counterpart in another context, system, or representation.
-
D.
hasCounterpart
Indicates that one entity corresponds to, matches, or serves as an equivalent or parallel version of another entity.
-
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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 29, 2026, 8:52 p.m.