Triple
T24884214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocktown |
E622803
|
entity |
| Predicate | hasCurrentFIPSCodeEntity |
P161424
|
FINISHED |
| Object | Harrisonburg, Virginia |
—
|
NE NERFINISHED |
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: Harrisonburg, Virginia | Statement: [Rocktown, hasCurrentFIPSCodeEntity, Harrisonburg, Virginia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrentFIPSCodeEntity Context triple: [Rocktown, hasCurrentFIPSCodeEntity, Harrisonburg, Virginia]
-
A.
FIPSCode
Indicates the standardized Federal Information Processing Standards (FIPS) code assigned to identify a specific geographic or administrative entity.
-
B.
hasCurrentAdministrativeEntity
Indicates that an entity is currently governed, managed, or overseen by a specific administrative body or authority.
-
C.
FIPSClass
Indicates the classification of an entity according to the Federal Information Processing Standards (FIPS) coding or category system.
-
D.
isCurrentISOCode
Indicates that an entity’s code is the officially recognized, up-to-date ISO standard code for that entity.
-
E.
hasFeatureCode
Indicates that an entity is associated with a specific feature identifier or code that characterizes one of its properties or attributes.
- F. None of above. chosen
Provenance (4 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_69e2fac4aa848190b3446a3922cec150 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f613bc641c819084343cc78d080640 |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f613502d808190b89927e5e734b43a |
completed | May 2, 2026, 3:08 p.m. |
Created at: April 18, 2026, 5:25 a.m.