Triple
T21237967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bártfa |
E523395
|
entity |
| Predicate | flourishedAsTradeCenterInCentury |
P143322
|
FINISHED |
| Object | 15th century |
—
|
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: 15th century | Statement: [Bártfa, flourishedAsTradeCenterInCentury, 15th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flourishedAsTradeCenterInCentury Context triple: [Bártfa, flourishedAsTradeCenterInCentury, 15th century]
-
A.
flourishedAsPortToCentury
Indicates that a port city experienced its peak activity or prosperity as a port during a specified century.
-
B.
flourishedAsPortFromCentury
Indicates that a place functioned successfully and prominently as a port starting from a specified century.
-
C.
flourishedToCentury
Indicates the century during which an entity reached its peak activity, prominence, or flourishing.
-
D.
flourishedInCentury
Indicates that an entity experienced its peak activity, influence, or development during a specified century.
-
E.
flourishedUntilCentury
Indicates the last century during which an entity (such as a person, culture, or institution) was active, prominent, or at its peak before declining or ceasing to flourish.
- F. None of above. chosen
Provenance (4 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_69e0b513b89c81908b27147e91368db2 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735212ad4819082d85f4d4342faf9 |
completed | April 21, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3:46 p.m.