Triple
T21353673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madison County, North Carolina |
E526553
|
entity |
| Predicate | hasCountyCodeFIPS |
P227
|
FINISHED |
| Object | 37115 |
—
|
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: 37115 | Statement: [Madison County, North Carolina, hasCountyCodeFIPS, 37115]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountyCodeFIPS Context triple: [Madison County, North Carolina, hasCountyCodeFIPS, 37115]
-
A.
hasCountyCode
Indicates that an entity is associated with a specific county identified by a standardized county code.
-
B.
hasCountyCodeType
Indicates that an entity is associated with a specific type or classification of county code.
-
C.
FIPSCode
chosen
Indicates the standardized Federal Information Processing Standards (FIPS) code assigned to identify a specific geographic or administrative entity.
-
D.
hasParentCounty
Indicates that a given county is administratively or geographically contained within, and subordinate to, a specified parent county.
-
E.
hasCountyEquivalentStatus
Indicates that an entity holds an administrative or legal status equivalent to that of a county within a given jurisdiction.
- 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_69e0b51cd5cc81909ac1187971e8a8ad |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69ee5bac9e1481909121e89f046c77f6 |
completed | April 26, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:05 p.m.