Triple
T25810009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ancaster |
E650079
|
entity |
| Predicate | establishedAsVillageYear |
P48685
|
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: [Ancaster, establishedAsVillageYear, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsVillageYear Context triple: [Ancaster, establishedAsVillageYear, 19th century]
-
A.
municipalityEstablished
Indicates that a municipality was officially created or founded at a specific point in time.
-
B.
eraOfEstablishment
chosen
Indicates the time period or historical era during which an entity was founded or established.
-
C.
wasFoundedAsTown
Indicates that an entity came into existence specifically with the legal or formal status of a town.
-
D.
settledInYear
Indicates the specific calendar year in which an entity became established, inhabited, or formally settled in a particular place or status.
-
E.
districtFormationYear
Indicates the year in which a district was officially established or formed.
- 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 22, 2026, 7:08 a.m.