Triple
T37336223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barton Township |
E926899
|
entity |
| Predicate | foundingLocationFor |
P4560
|
FINISHED |
| Object | town of Hamilton |
—
|
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: town of Hamilton | Statement: [Barton Township, foundingLocationFor, town of Hamilton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundingLocationFor Context triple: [Barton Township, foundingLocationFor, town of Hamilton]
-
A.
foundingLocationOfFoundedOrganization
Indicates the place where an organization was originally established or founded.
-
B.
foundingLocationPresentCountry
Indicates the present-day country in which the location where something (typically an organization or institution) was founded is situated.
-
C.
placeFounded
chosen
Indicates the location where an entity (such as an organization or institution) was originally established or founded.
-
D.
foundedNear
Indicates that one entity established or created another entity at a location geographically close to a specified reference entity or place.
-
E.
locatedInCityFoundedFor
Indicates that something is located in a city that was specifically founded for that thing or for its primary purpose.
- 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_69f76eb4e8a881908bd40da28f36fc7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
Created at: May 3, 2026, 4:16 p.m.