Triple
T34125729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corcoran |
E875269
|
entity |
| Predicate | hasPrisonNearby |
P21915
|
FINISHED |
| Object | California State Prison, Corcoran |
E401271
|
NE 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: California State Prison, Corcoran | Statement: [Corcoran, hasPrisonNearby, California State Prison, Corcoran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrisonNearby Context triple: [Corcoran, hasPrisonNearby, California State Prison, Corcoran]
-
A.
hasNearbyPrisonComplex
Indicates that one location is situated close to a prison complex.
-
B.
hasPrison
chosen
Indicates that one entity possesses, contains, or is the location of a prison associated with another entity.
-
C.
hasNearbyInnOfCourt
Indicates that one entity is located close to, or in the immediate vicinity of, an Inn of Court.
-
D.
isPrisonComplex
Indicates that an entity functions as a prison facility or complex used for the confinement and management of incarcerated individuals.
-
E.
prisonLocatedIn
Indicates that a prison is situated within or at a specific geographic or administrative location.
- F. None of above.
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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a02efcb13248190a0bef09ba7869ada |
completed | May 12, 2026, 9:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36c1c312e48190bef308aaa947f91c |
completed | June 20, 2026, 4:37 p.m. |
| PD | Predicate disambiguation | batch_6a024995e1d081908783ca294d1397c3 |
completed | May 11, 2026, 9:26 p.m. |
Created at: May 1, 2026, 1:53 a.m.