Triple
T11207685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plainview, Tennessee |
E265213
|
entity |
| Predicate | ruralMunicipalityType |
P10835
|
FINISHED |
| Object | rural community |
—
|
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: rural community | Statement: [Plainview, Tennessee, ruralMunicipalityType, rural community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruralMunicipalityType Context triple: [Plainview, Tennessee, ruralMunicipalityType, rural community]
-
A.
isRuralMunicipalityOf
Indicates that one entity is a rural municipality that is administratively or geographically part of, or governed by, another entity.
-
B.
countyType
Indicates the classification or category of a county within an administrative or governmental system.
-
C.
hasMunicipalityType
chosen
Indicates that an administrative unit is classified as having a specific type or category of municipality (e.g., city, town, village).
-
D.
localGovernmentAreaType
Indicates the specific classification or category of a local government area within an administrative or governmental hierarchy.
-
E.
typeOfDistrict
Indicates the specific category or classification to which a given district belongs.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8d5f8908190903817f84c629ba1 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.