Triple
T33159835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lamar, Indiana |
E848694
|
entity |
| Predicate | withinUSCounty |
P23957
|
FINISHED |
| Object | Perry County |
—
|
NE NERFINISHED |
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: Perry County | Statement: [Lamar, Indiana, withinUSCounty, Perry County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: withinUSCounty Context triple: [Lamar, Indiana, withinUSCounty, Perry County]
-
A.
inCounty
chosen
Indicates that one entity is geographically or administratively located within the boundaries of a specified county.
-
B.
isNamedCountyOf
Indicates that a county bears a specific official name within a given jurisdiction or context.
-
C.
includesCounty
Indicates that a larger geographic or administrative region contains or encompasses a specific county within its boundaries.
-
D.
isCornerCountyOf
Indicates that a county lies at or near the corner where two or more larger administrative regions (such as states or districts) meet.
-
E.
inlandCounty
Indicates that a county is located away from the coast, without direct access to a sea or ocean.
- 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_69f3495b02d08190bb3d366823dffc21 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:28 a.m.