Triple
T974025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Infirmary Command |
E21008
|
entity |
| Predicate | hasPopulationSubset |
P5947
|
FINISHED |
| Object | inmates in protective custody |
—
|
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: inmates in protective custody | Statement: [North Infirmary Command, hasPopulationSubset, inmates in protective custody]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPopulationSubset Context triple: [North Infirmary Command, hasPopulationSubset, inmates in protective custody]
-
A.
hasSubset
Indicates that one set is entirely contained within another set, with all elements of the first set also belonging to the second.
-
B.
hasPopulationType
chosen
Indicates that an entity’s population is classified according to a specific type or category (e.g., demographic, biological, or statistical grouping).
-
C.
hasSubdivision
Indicates that one entity is divided into and contains another entity as one of its constituent parts or administrative units.
-
D.
hasSubcommunityIn
Indicates that a larger community contains or encompasses a smaller, distinct subcommunity located within it.
-
E.
hasMinorityIn
Indicates that one entity holds a non-controlling, minority ownership or stake in another entity.
- 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_69a493c2b62c8190b616351789ec47f8 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b45f28f081908d41b2d7f353708d |
completed | March 1, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a6aa2c8190aebba71320ab678f |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.