Triple
T26657461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strawberry Fields |
E666546
|
entity |
| Predicate | killedInWork |
P161095
|
FINISHED |
| Object | Quantum of Solace |
—
|
NE NERFINISHED |
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: Quantum of Solace | Statement: [Strawberry Fields, killedInWork, Quantum of Solace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: killedInWork Context triple: [Strawberry Fields, killedInWork, Quantum of Solace]
-
A.
killedDuring
Indicates that one entity caused the death of another entity in the course of, or as part of, a specified event or time period.
-
B.
killedBy
Indicates that one entity caused the death of another entity.
-
C.
killedBecauseOf
Indicates that one entity killed another specifically due to a particular reason, motive, or triggering factor associated with that other entity or a related circumstance.
-
D.
killedInAttack
Indicates that an entity died as a direct result of a specific attack event.
-
E.
killedNear
Indicates that one entity killed another in close spatial proximity to a specified location or reference point.
- F. None of above. chosen
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_69ee9cf8c7188190b9b00270a8a89164 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f616bb8574819087339f6e25346d2c |
completed | May 2, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60f24ed608190bffe6c6084fc2f7a |
completed | May 2, 2026, 2:50 p.m. |
Created at: April 27, 2026, 2:35 a.m.