Triple
T24070374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sing Sing Prison |
E596208
|
entity |
| Predicate | executionFunctionEnded |
P56380
|
FINISHED |
| Object | 1963 |
—
|
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: 1963 | Statement: [Sing Sing Prison, executionFunctionEnded, 1963]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: executionFunctionEnded Context triple: [Sing Sing Prison, executionFunctionEnded, 1963]
-
A.
functionEnd
chosen
Indicates the point or condition at which a function, process, or operation terminates or completes.
-
B.
endedFunctionallyWith
Indicates that a process, event, or relationship has effectively concluded in practice, even if it has not been formally or officially terminated.
-
C.
executionEngine
Indicates the mechanism or component responsible for carrying out, managing, or running a defined process, task, or set of operations.
-
D.
developmentEnded
Indicates that the process of creating, improving, or expanding something has been completed and no further development is taking place.
-
E.
executionBy
Indicates that one entity carries out or performs the execution (killing or implementation of a death sentence) of 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_69e288c25c008190850cf447940ab181 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1db17c99881909f97e858fb183d86 |
completed | April 29, 2026, 10:19 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:41 p.m.