Triple
T30977586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanseatic merchants |
E789269
|
entity |
| Predicate | maintainedKontor |
P35801
|
FINISHED |
| Object | Steelyard in London |
—
|
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: Steelyard in London | Statement: [Hanseatic merchants, maintainedKontor, Steelyard in London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainedKontor Context triple: [Hanseatic merchants, maintainedKontor, Steelyard in London]
-
A.
hadKontorIn
chosen
Indicates that an entity maintained or operated a commercial office or trading post in a specified location.
-
B.
maintainedDespite
Indicates that a condition, relationship, or state continues to hold or remain in effect even though some opposing, challenging, or changing factor is present.
-
C.
maintainedFor
Indicates that something is kept in a particular state, condition, or operation for the benefit, use, or purpose of another entity.
-
D.
legacyMaintainedBy
Indicates that responsibility for preserving, continuing, or upholding a legacy rests with a particular entity.
-
E.
keptIn
Indicates that one entity is stored, contained, or maintained inside another entity as its location or container.
- 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 29, 2026, 8:55 p.m.