Triple
T17970054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIPS 04-07910 |
E449311
|
entity |
| Predicate | placeFIPSCode |
P227
|
FINISHED |
| Object | 07910 |
—
|
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: 07910 | Statement: [FIPS 04-07910, placeFIPSCode, 07910]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeFIPSCode Context triple: [FIPS 04-07910, placeFIPSCode, 07910]
-
A.
FIPSCode
chosen
Indicates the standardized Federal Information Processing Standards (FIPS) code assigned to identify a specific geographic or administrative entity.
-
B.
locationCode
Indicates the specific coded location associated with an entity, event, or relationship.
-
C.
districtCode
Indicates that an entity is associated with, or identified by, a specific administrative district code.
-
D.
hasCountyCode
Indicates that an entity is associated with a specific county identified by a standardized county code.
-
E.
countyOfPlace
Indicates that a place is located within or administratively belongs to a specific county.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b13b1b088190b7d71006b31e5cc3 |
completed | April 19, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.