Triple
T28923904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Justice Lawrence Wargrave |
E733591
|
entity |
| Predicate | plansMurdersToMatch |
P166254
|
FINISHED |
| Object | Ten Little Soldiers nursery rhyme |
—
|
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: Ten Little Soldiers nursery rhyme | Statement: [Justice Lawrence Wargrave, plansMurdersToMatch, Ten Little Soldiers nursery rhyme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plansMurdersToMatch Context triple: [Justice Lawrence Wargrave, plansMurdersToMatch, Ten Little Soldiers nursery rhyme]
-
A.
methodOfMurderScheme
Indicates the specific method or scheme by which a murder is carried out in a given situation or plan.
-
B.
plansRobberyIn
Indicates that an entity is preparing or organizing to commit a robbery within a specified location or jurisdiction.
-
C.
reasonForMurder
Indicates the motive or underlying cause that led someone to commit a murder.
-
D.
hasPartInMurderOf
Indicates involvement as a contributing participant in the commission of a murder.
-
E.
plansKidnappingOf
Indicates that one entity is formulating or organizing a plan to abduct another entity against their will.
- 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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 8:22 a.m.