Triple
T17766631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ravenna, Ohio |
E443523
|
entity |
| Predicate | primaryCountyFunctions |
P82325
|
FINISHED |
| Object | judicial services |
—
|
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: judicial services | Statement: [Ravenna, Ohio, primaryCountyFunctions, judicial services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCountyFunctions Context triple: [Ravenna, Ohio, primaryCountyFunctions, judicial services]
-
A.
primaryCountyServicesLocation
Indicates the location that serves as the main site where county-level services are provided or administered.
-
B.
countyFunction
chosen
Indicates that a county serves a particular administrative or governmental role or performs a specified function.
-
C.
primaryCountyOfParentMunicipality
Indicates that a given county is the main or principal county in which the parent municipality of an entity is located.
-
D.
majorCounty
Indicates that a county holds primary or significant administrative, economic, or demographic importance within a larger region or jurisdiction.
-
E.
governmentalFunction
Indicates that an entity performs, embodies, or is responsible for an official role, duty, or activity of a government.
- 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.