Triple
T8874843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tioga, New York |
E211247
|
entity |
| Predicate | isInCountyNamed |
P23957
|
FINISHED |
| Object | Tioga 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: Tioga County | Statement: [Tioga, New York, isInCountyNamed, Tioga County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInCountyNamed Context triple: [Tioga, New York, isInCountyNamed, Tioga County]
-
A.
isInCountySeatOf
Indicates that one entity is located within the town or city that serves as the administrative center (county seat) of a specified county.
-
B.
isInCountySeat
Indicates that one entity (typically a place or facility) is located within the county seat of a given county.
-
C.
isInCountySubdivision
Indicates that one entity (typically a place or address) is located within the boundaries of a specific county subdivision.
-
D.
inCounty
chosen
Indicates that one entity is geographically or administratively located within the boundaries of a specified county.
-
E.
includesCounty
Indicates that a larger geographic or administrative region contains or encompasses a specific county within its boundaries.
- 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_69ca838e78748190934d82db3104f855 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc614451d081908804430a72d00edf |
completed | April 1, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2956788190a311c647b4da17a6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:52 p.m.