Triple
T745280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Łódź |
E15327
|
entity |
| Predicate | experiencedRapidGrowthInCentury |
P18582
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Łódź, experiencedRapidGrowthInCentury, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experiencedRapidGrowthInCentury Context triple: [Łódź, experiencedRapidGrowthInCentury, 19th century]
-
A.
statusIn20thCentury
Indicates that an entity held a particular status, condition, or classification specifically during the 20th century.
-
B.
century
Indicates that an entity is associated with, occurs in, or belongs to a particular 100-year time period.
-
C.
foundedInCentury
Indicates that an entity was established or came into existence during a specified century.
-
D.
usedSinceCentury
Indicates that something has been in use starting from a specified century.
-
E.
endedInCentury
Indicates that an event, period, or process concluded during a specified century.
- 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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a61217b881908592096b1edacb8a |
completed | March 1, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69a4a4ff10608190bfd60b4a1cb38f7d |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a57267c481909790a1fda3fced08 |
completed | March 1, 2026, 8:45 p.m. |
Created at: March 1, 2026, 7:37 p.m.