Triple
T27548577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1962 Alcatraz escape |
E695428
|
entity |
| Predicate | localPoliceCaseStatus |
P47732
|
FINISHED |
| Object | open |
—
|
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: open | Statement: [1962 Alcatraz escape, localPoliceCaseStatus, open]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localPoliceCaseStatus Context triple: [1962 Alcatraz escape, localPoliceCaseStatus, open]
-
A.
lawEnforcementStatus
chosen
Indicates the relationship between an entity and its current standing or condition with respect to law enforcement, such as being under investigation, wanted, detained, or cleared.
-
B.
criminalStatus
Indicates the legal condition of an entity with respect to criminal law, such as whether they are accused, convicted, or cleared of a crime.
-
C.
statusInColumbo
Indicates that an entity holds a particular status, role, or condition specifically within the context of Columbo.
-
D.
courtStatus
Indicates the current legal or procedural state of a case or matter within a court system.
-
E.
statusInLegalSystem
Indicates the current standing or condition of an entity within a legal or judicial framework (e.g., pending, active, resolved, or appealed).
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 1:34 p.m.