Triple
T9481565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Davenport, California |
E228651
|
entity |
| Predicate | cementPlantStatus |
P5870
|
FINISHED |
| Object | closed |
—
|
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: closed | Statement: [Davenport, California, cementPlantStatus, closed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cementPlantStatus Context triple: [Davenport, California, cementPlantStatus, closed]
-
A.
hasIndustrialPlant
Indicates that an entity possesses, operates, or is associated with an industrial plant facility.
-
B.
classStatus
Indicates the current academic or enrollment standing of an entity within a class or course context.
-
C.
operatingStatus
chosen
Indicates whether an entity is currently functioning, active, or in service versus inactive, closed, or out of service.
-
D.
cultivationStatus
Indicates the current state or condition of an entity with respect to being cultivated, such as whether and how it is actively grown or managed.
-
E.
maintenanceStatus
Indicates the current state or condition of an entity with respect to its maintenance activities, such as whether it is pending, in progress, completed, or overdue.
- 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_69ca84730a5081908de282651019bf2f |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd804af6d08190a281cb27407c791c |
completed | April 1, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69cca561e6b0819090aa795f3c3a2083 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:55 p.m.