Triple
T27151997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troutman |
E682413
|
entity |
| Predicate | FIPScodeCounty |
P10086
|
FINISHED |
| Object | 097 |
—
|
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: 097 | Statement: [Troutman, FIPScodeCounty, 097]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FIPScodeCounty Context triple: [Troutman, FIPScodeCounty, 097]
-
A.
FIPSCode
Indicates the standardized Federal Information Processing Standards (FIPS) code assigned to identify a specific geographic or administrative entity.
-
B.
hasCountyCode
chosen
Indicates that an entity is associated with a specific county identified by a standardized county code.
-
C.
USStateFIPSLocation
Indicates a locational relationship where a place or entity is situated within, or associated with, a U.S. state identified by its FIPS (Federal Information Processing Standards) code.
-
D.
hasCountyCodeType
Indicates that an entity is associated with a specific type or classification of county code.
-
E.
hasCurrentFIPSCodeEntity
Indicates that an entity is associated with a specific, currently valid FIPS (Federal Information Processing Standards) code.
- 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6250321088190ae3ed1dc9f2fcd03 |
completed | May 2, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:14 a.m.