Triple
T7470307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fulton County, New York |
E176484
|
entity |
| Predicate | fipsCodeState |
P227
|
FINISHED |
| Object | 36 |
—
|
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: 36 | Statement: [Fulton County, New York, fipsCodeState, 36]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fipsCodeState Context triple: [Fulton County, New York, fipsCodeState, 36]
-
A.
FIPSCode
chosen
Indicates the standardized Federal Information Processing Standards (FIPS) code assigned to identify a specific geographic or administrative entity.
-
B.
stateSubdivisionCode
Indicates the standardized code that identifies a specific subdivision (such as a state, province, or region) within a larger country or territory.
-
C.
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.
-
D.
stateFederation
Indicates that a state is a member of, or participates in, a larger federal union or federation.
-
E.
keyUSState
Indicates that a U.S. state plays a primary or strategically important role in a given context (such as politics, economy, or policy).
- 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_69c69f223fd88190b4c69b95d7cbeeda |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f4145d608190bd93239f04f7da41 |
completed | March 27, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69c6f03d967081908a8e696ff9693b90 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:41 p.m.