Triple
T5428957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Visby |
E121435
|
entity |
| Predicate | flourishedAsHanseaticCenter |
P46886
|
FINISHED |
| Object | 12th–14th centuries |
—
|
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: 12th–14th centuries | Statement: [Visby, flourishedAsHanseaticCenter, 12th–14th centuries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flourishedAsHanseaticCenter Context triple: [Visby, flourishedAsHanseaticCenter, 12th–14th centuries]
-
A.
flourishedIn
Indicates that an entity experienced its peak activity, success, or prominence during a specified time period or era.
-
B.
flourishedAmong
Indicates that an entity thrived, prospered, or reached a peak of development within a particular group, environment, or context.
-
C.
flourishedAs
chosen
Indicates that an entity thrived, prospered, or reached a peak state in the role, capacity, or form specified by another entity.
-
D.
flourishedToCentury
Indicates the century during which an entity reached its peak activity, prominence, or flourishing.
-
E.
flourishedInCentury
Indicates that an entity experienced its peak activity, influence, or development during a specified century.
- 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_69bd463c65f0819082ee6483ab4b466a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8911a7348190ad9378a248190f07 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd846b8bdc81909dcdc2a3084226f2 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:06 p.m.