Triple
T33858613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Center, Indiana |
E867858
|
entity |
| Predicate | usesCountyServices |
P192058
|
FINISHED |
| Object | Noble County 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: Noble County services | Statement: [Green Center, Indiana, usesCountyServices, Noble County services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCountyServices Context triple: [Green Center, Indiana, usesCountyServices, Noble County services]
-
A.
usedForCounty
Indicates that something serves as or is designated for use by a particular county.
-
B.
primaryCountyServicesLocation
Indicates the location that serves as the main site where county-level services are provided or administered.
-
C.
usedInCounty
chosen
Indicates that something is utilized, applied, or in operation within the jurisdiction or geographic boundaries of a specific county.
-
D.
servesCountyTown
Indicates that an entity (such as a service, office, or facility) provides coverage or service to a specified county or town.
-
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_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: May 1, 2026, 1:47 a.m.