Triple
T5049789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hartley, California |
E113755
|
entity |
| Predicate | isCensusDesignated |
P43597
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hartley, California, isCensusDesignated, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCensusDesignated Context triple: [Hartley, California, isCensusDesignated, true]
-
A.
containsCensusDesignatedPlace
Indicates that one geographic or administrative area includes within its boundaries a census-designated place.
-
B.
censusDesignatedPlace
chosen
Indicates that an entity is classified as a census-designated place, i.e., a populated area defined for statistical purposes by a census authority.
-
C.
hasCriticalDesignation
Indicates that an entity has been assigned a status or label marking it as critical in importance, priority, or required attention.
-
D.
includedInCensus
Indicates that an entity was recorded or counted as part of a specific census.
-
E.
hasCityDesignatedAs
Indicates that an entity has a specific city formally assigned or designated to it in a particular role or capacity.
- 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7425df74819091cfde348dd16a68 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd715479f08190933604aebd34414f |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.