Triple
T19675881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harrison, Nebraska |
E472450
|
entity |
| Predicate | plattedIn |
P86135
|
FINISHED |
| Object | 1886 |
—
|
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: 1886 | Statement: [Harrison, Nebraska, plattedIn, 1886]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plattedIn Context triple: [Harrison, Nebraska, plattedIn, 1886]
-
A.
platted
chosen
Indicates that an area of land has been formally mapped and subdivided into lots or parcels, typically for development or sale.
-
B.
originallyPlattedBy
Indicates that one entity is the person or organization that first laid out, mapped, or formally subdivided the other entity (such as a town or parcel of land) into lots or plots.
-
C.
isPlannedCommunity
Indicates that a community has been intentionally designed and developed according to a coordinated plan rather than growing organically.
-
D.
townPlannedWith
Indicates that a town was designed, organized, or laid out in coordination with a particular plan, entity, or planning effort.
-
E.
urbanPlanApproved
Indicates that an official authority has reviewed and formally authorized a proposed urban development or land-use plan.
- 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e641bbea8c8190b0ad841d95068e0e |
completed | April 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69e514eb37b8819091502cc954f70eba |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:45 p.m.