Triple
T14500006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karabük |
E359608
|
entity |
| Predicate | foundedAsIndustrialTown |
P114476
|
FINISHED |
| Object | 20th 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: 20th century | Statement: [Karabük, foundedAsIndustrialTown, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsIndustrialTown Context triple: [Karabük, foundedAsIndustrialTown, 20th century]
-
A.
hasIndustrialTown
Indicates that an entity possesses or is associated with a town characterized primarily by industrial activities or facilities.
-
B.
formerIndustrialTown
Indicates that a town previously had a significant industrial base or economy but no longer does.
-
C.
wasFoundedAsTown
Indicates that an entity came into existence specifically with the legal or formal status of a town.
-
D.
isEarlyIndustrialCentreOf
Indicates that a place functioned as an important center of early industrial activity for another specified region or context.
-
E.
foundingAsRailroadTown
Indicates that a settlement was originally established specifically to serve or develop around a railroad line or station.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de94dfe484819086dd971606e6478e |
completed | April 14, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:21 a.m.