Triple
T5262983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramla Prison |
E118869
|
entity |
| Predicate | executionMethodUsed |
P2301
|
FINISHED |
| Object | hanging |
—
|
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: hanging | Statement: [Ramla Prison, executionMethodUsed, hanging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: executionMethodUsed Context triple: [Ramla Prison, executionMethodUsed, hanging]
-
A.
executedWith
chosen
Indicates that an action or process was carried out using, accompanied by, or in conjunction with a specified tool, method, or participant.
-
B.
executionBy
Indicates that one entity carries out or performs the execution (killing or implementation of a death sentence) of another entity.
-
C.
executionEngine
Indicates the mechanism or component responsible for carrying out, managing, or running a defined process, task, or set of operations.
-
D.
executionModel
Indicates how a process, task, or operation is carried out or implemented, specifying the underlying method, strategy, or mechanism of its execution.
-
E.
executedIn
Indicates that an action or process is carried out or takes place within a specified location, context, or environment.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bd2eff4819087420e30c140e6f6 |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:51 p.m.