Triple
T10601863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freeland, Washington |
E275766
|
entity |
| Predicate | CDPStatus |
P94873
|
FINISHED |
| Object | recognized by U.S. Census Bureau |
—
|
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: recognized by U.S. Census Bureau | Statement: [Freeland, Washington, CDPStatus, recognized by U.S. Census Bureau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CDPStatus Context triple: [Freeland, Washington, CDPStatus, recognized by U.S. Census Bureau]
-
A.
HDIStatus
Indicates the classification of a country or region according to its Human Development Index (HDI) level, such as low, medium, high, or very high human development.
-
B.
classStatus
Indicates the current academic or enrollment standing of an entity within a class or course context.
-
C.
DOCStatus
Indicates the current state or condition of a document within a defined process or lifecycle.
-
D.
covenantStatus
Indicates the current state or condition of a covenant or binding agreement between parties.
-
E.
CISStatus
Indicates the compliance or certification status of an entity with respect to CIS (Center for Internet Security) benchmarks or standards.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df4992248190b640d743ccf02c82 |
completed | April 8, 2026, 11:05 p.m. |
| PD | Predicate disambiguation | batch_69d6dd72c1288190adbb5e79e94c044a |
completed | April 8, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d6df463ea8819091d6683e476b4f21 |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 7:31 p.m.