Triple
T21744810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Town of Truro |
E536758
|
entity |
| Predicate | foundedAsSettlementInCentury |
P120764
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Town of Truro, foundedAsSettlementInCentury, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsSettlementInCentury Context triple: [Town of Truro, foundedAsSettlementInCentury, 18th century]
-
A.
settledInCentury
chosen
Indicates that an entity’s act of settling or establishment occurred during a specified century.
-
B.
foundedAsModernSettlement
Indicates that one entity was established or created as a modern-era settlement, rather than originating as an ancient or historical habitation.
-
C.
foundedAsSettlementFor
Indicates that one entity was originally established specifically to serve as a settlement for another entity (such as a group, population, or community).
-
D.
earliestEuropeanSettlementCentury
Indicates the century during which the earliest European settlement associated with the subject was established.
-
E.
foundedInCentury
Indicates that an entity was established or came into existence during a specified century.
- 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_69e0c46df5448190b4322127ffc4c690 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01a75352c8190bcd46759562ee251 |
completed | April 28, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:49 p.m.