Triple
T31291973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Kingdom and the Netherlands |
E797964
|
entity |
| Predicate | haveHistoricalConnections |
P7843
|
FINISHED |
| Object | medieval trade |
—
|
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: medieval trade | Statement: [United Kingdom and the Netherlands, haveHistoricalConnections, medieval trade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveHistoricalConnections Context triple: [United Kingdom and the Netherlands, haveHistoricalConnections, medieval trade]
-
A.
historicalContactWith
Indicates that two entities have interacted or been in communication with each other at some point in the past.
-
B.
hasNegativeHistoricalAssociation
Indicates that one entity is historically linked to another in a way that is viewed as harmful, problematic, or disreputable.
-
C.
hasHeritageConnectionWith
Indicates a relationship where two entities are linked through shared, inherited, or culturally transmitted heritage or ancestry.
-
D.
hasHistoricalTieTo
chosen
Indicates a relationship where one entity is historically connected or linked to another through past events, associations, or influences.
-
E.
formerlyConnectedTo
Indicates that two entities were once connected or associated in some way, but that connection no longer exists.
- 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_69f224dfde288190af313f3c221c857e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:14 p.m.