Triple
T8481808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon State Penitentiary |
E200536
|
entity |
| Predicate | hasNumberOfInmates |
P14018
|
FINISHED |
| Object | over 2000 |
—
|
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: over 2000 | Statement: [Oregon State Penitentiary, hasNumberOfInmates, over 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfInmates Context triple: [Oregon State Penitentiary, hasNumberOfInmates, over 2000]
-
A.
numberOfPrisonersApproximate
Indicates an approximate count of prisoners associated with an entity or situation, rather than an exact number.
-
B.
estimatedPrisonerCount
chosen
Indicates the estimated number of prisoners associated with a particular context, such as a location, time period, or event.
-
C.
hasPrisonerPopulation
Indicates that an entity maintains or contains a population of prisoners, specifying the number or presence of incarcerated individuals associated with it.
-
D.
hasPrisoners
Indicates that an entity holds or contains one or more individuals who are imprisoned or detained.
-
E.
inmates
Indicates that one entity is confined or held as a prisoner within an institution or facility associated with 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_69ca831b17988190a1f3f3413d57b820 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe53638c48190b742fc51d1b4442a |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd104250c8190b4c499dcc9937494 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:12 p.m.