Triple
T5395106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sherman, Connecticut |
E120632
|
entity |
| Predicate | hasCensusStatus |
P53267
|
FINISHED |
| Object | census-designated place |
—
|
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: census-designated place | Statement: [Sherman, Connecticut, hasCensusStatus, census-designated place]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCensusStatus Context triple: [Sherman, Connecticut, hasCensusStatus, census-designated place]
-
A.
includedInCensus
chosen
Indicates that an entity was recorded or counted as part of a specific census.
-
B.
hasPopulationStatus
Indicates the current demographic condition or classification of a population associated with an entity.
-
C.
censusNumber
Indicates the unique identifier or count assigned to an entity within an official census record.
-
D.
census
Indicates that an official count or survey is conducted to determine the number and characteristics of a population within a defined area or group.
-
E.
censusReportedIn
Indicates that information about a population or demographic count is documented or recorded in a specific census.
- 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_69bd4637b92c8190b815b6443ae4b323 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8745c10c8190afa72894014c37d1 |
completed | March 20, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:04 p.m.