Triple
T17766640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ravenna, Ohio |
E443523
|
entity |
| Predicate | isCountySeatSince |
P26682
|
FINISHED |
| Object | early 19th century |
—
|
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: early 19th century | Statement: [Ravenna, Ohio, isCountySeatSince, early 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCountySeatSince Context triple: [Ravenna, Ohio, isCountySeatSince, early 19th century]
-
A.
countySeatSince
chosen
Indicates that one place has served as the official county seat of a county starting from a specified point in time.
-
B.
foundedAsCountySeat
Indicates that a place was originally established or designated to serve as the administrative center (county seat) of a county.
-
C.
hasCountySeatSuccessor
Indicates that one county seat has been succeeded or replaced by another as the official administrative center for a county.
-
D.
hasCountySeatCity
Indicates that a county has a specific city that serves as its official administrative center or county seat.
-
E.
hasCountySeatRelation
Indicates that a specific place serves as the county seat (administrative center) of a particular county.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e485fccb9881908923564bf319f3c1 |
completed | April 19, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:11 a.m.