Triple
T459332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pueblo Chemical Depot |
E7301
|
entity |
| Predicate | typeOfSite |
P15047
|
FINISHED |
| Object | ammunition depot |
—
|
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: ammunition depot | Statement: [Pueblo Chemical Depot, typeOfSite, ammunition depot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfSite Context triple: [Pueblo Chemical Depot, typeOfSite, ammunition depot]
-
A.
siteTypeServed
Indicates the type of site or location that is served, supported, or handled by a given entity or resource.
-
B.
site
Indicates that one entity is the physical or virtual location where another entity is situated, occurs, or is based.
-
C.
coversTypeOfSite
Indicates that one entity provides coverage or applies to a particular category or type of site.
-
D.
website
Indicates that one entity is the official website or web presence associated with another entity.
-
E.
containsSite
Indicates that one entity spatially or structurally includes another entity as a site or location within its bounds.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efa4a6208190a8243a0e14f84f52 |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede75b6c81908350103d21f22a03 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2ef257a548190a96bfa0cf6183976 |
completed | Feb. 28, 2026, 1:35 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.