Triple
T16983702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lee County, Mississippi |
E412006
|
entity |
| Predicate | US state FIPS code |
P227
|
FINISHED |
| Object | 28 |
—
|
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: 28 | Statement: [Lee County, Mississippi, US state FIPS code, 28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: US state FIPS code Context triple: [Lee County, Mississippi, US state FIPS code, 28]
-
A.
FIPSCode
chosen
Indicates the standardized Federal Information Processing Standards (FIPS) code assigned to identify a specific geographic or administrative entity.
-
B.
federalStateCode
Indicates that an entity is associated with, governed by, or identified through a specific federal state code within a country’s administrative or legal system.
-
C.
keyUSState
Indicates that a U.S. state plays a primary or strategically important role in a given context (such as politics, economy, or policy).
-
D.
FIPSCountryCode
Indicates that an entity is associated with a specific country as identified by its FIPS (Federal Information Processing Standards) country code.
-
E.
includesFederalState
Indicates that one entity encompasses or contains both federal-level and state-level components, jurisdictions, or elements.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d188ede48190baead48aac84c78d |
completed | April 18, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.