Triple
T23145039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boardman |
E577563
|
entity |
| Predicate | foundedAsTownship |
P4622
|
FINISHED |
| Object | 1806 |
—
|
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: 1806 | Statement: [Boardman, foundedAsTownship, 1806]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsTownship Context triple: [Boardman, foundedAsTownship, 1806]
-
A.
wasFoundedAsTown
Indicates that an entity came into existence specifically with the legal or formal status of a town.
-
B.
foundedAsCounty
Indicates that an administrative region or jurisdiction was originally established with the legal status and designation of a county.
-
C.
foundedAsCountySeat
Indicates that a place was originally established or designated to serve as the administrative center (county seat) of a county.
-
D.
incorporatedAsTownship
chosen
Indicates that an area or community has been formally established and recognized as a township through a legal or governmental incorporation process.
-
E.
foundingAsMissionTown
Indicates the event in which a settlement is established specifically as a mission town, i.e., founded with the primary purpose of serving as a religious mission community.
- 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_69e245f8e6248190ba3d58e068b4dccb |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18ecd40108190aaad7faf754b7936 |
completed | April 29, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:01 p.m.