Triple
T37256936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trial of the Century |
E924155
|
entity |
| Predicate | hasVictimFamilyMember |
P59760
|
FINISHED |
| Object | Charles Lindbergh |
—
|
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: Charles Lindbergh | Statement: [Trial of the Century, hasVictimFamilyMember, Charles Lindbergh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVictimFamilyMember Context triple: [Trial of the Century, hasVictimFamilyMember, Charles Lindbergh]
-
A.
hasVictimSpouse
Indicates that a person’s spouse is the victim in a harmful, criminal, or adverse event involving that person.
-
B.
isVictimOf
Indicates that one entity suffers harm, loss, or wrongdoing as a result of another entity’s actions or events.
-
C.
hasProtagonistFamilyMember
Indicates that a work’s protagonist has a specified individual as a member of their family.
-
D.
hasVictims
chosen
Indicates that an entity has one or more individuals who have been harmed, injured, or adversely affected by it.
-
E.
hasMainVictim
Indicates that an event, action, or harmful situation primarily targets or affects a specific victim as its main subject.
- 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
Created at: May 3, 2026, 4:15 p.m.