Triple
T8726129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lahti |
E207135
|
entity |
| Predicate | foundedAsMarketTown |
P17485
|
FINISHED |
| Object | 1878 |
—
|
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: 1878 | Statement: [Lahti, foundedAsMarketTown, 1878]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsMarketTown Context triple: [Lahti, foundedAsMarketTown, 1878]
-
A.
wasFoundedAsTown
Indicates that an entity came into existence specifically with the legal or formal status of a town.
-
B.
hasMarketTownHistory
chosen
Indicates that an entity has a historical association with functioning as a market town or possessing recognized market-town status in the past.
-
C.
hasMarketTownStatus
Indicates that a settlement holds the official legal or historical status of being recognized as a market town.
-
D.
foundedAsCountySeat
Indicates that a place was originally established or designated to serve as the administrative center (county seat) of a county.
-
E.
foundedAs
Indicates the original name or form under which an organization, institution, or entity was first established.
- 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d158b0481908249610458f97306 |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:36 p.m.