Triple
T24884210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocktown |
E622803
|
entity |
| Predicate | hasCurrentPopulationEntity |
P159696
|
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, hasCurrentPopulationEntity, Harrisonburg, Virginia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrentPopulationEntity Context triple: [Rocktown, hasCurrentPopulationEntity, Harrisonburg, Virginia]
-
A.
hasCurrentPopulationPlace
Indicates that a place currently has a specified population value or population-related attribute.
-
B.
hasPopulationStatus
Indicates the current demographic condition or classification of a population associated with an entity.
-
C.
currentPopulation
Indicates the present number of individuals living in or belonging to a specified entity (such as a location or group).
-
D.
hasPopulationAsOf
Indicates that a population count is associated with a specific point or date in time when that population figure was valid or recorded.
-
E.
hasResidentPopulation
Indicates that a place or administrative area has a population of people who live there permanently or for an extended period.
- 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_69f5f7a205688190b8f36bff5013247c |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 18, 2026, 5:25 a.m.