Triple
T33956776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flagtown |
E870594
|
entity |
| Predicate | CDPDesignationEffectiveFor |
P157027
|
FINISHED |
| Object | 2020 Census |
—
|
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: 2020 Census | Statement: [Flagtown, CDPDesignationEffectiveFor, 2020 Census]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CDPDesignationEffectiveFor Context triple: [Flagtown, CDPDesignationEffectiveFor, 2020 Census]
-
A.
censusDesignationBy
chosen
Indicates that an entity has been assigned a particular census designation by a specified authority or source.
-
B.
hasRegionDesignation
Indicates that an entity is assigned or associated with a specific regional classification or designation.
-
C.
scenicDesignationStatus
Indicates the formal status or classification of an entity regarding its recognition or protection as a scenic or visually significant area or route.
-
D.
environmentDesignation
Indicates that an entity is assigned a specific environmental classification or status within a given context.
-
E.
stateDesignation
Indicates that an entity has been formally assigned or recognized with a particular status, title, or classification by an official authority or governing body.
- 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_69f3499c2d7481909c953a5010227725 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:49 a.m.