Triple
T37459635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malorne |
E930884
|
entity |
| Predicate | deathSound |
P190106
|
FINISHED |
| Object | Unique Malorne death line |
—
|
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: Unique Malorne death line | Statement: [Malorne, deathSound, Unique Malorne death line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathSound Context triple: [Malorne, deathSound, Unique Malorne death line]
-
A.
deathBy
Indicates a relationship where one entity’s death is caused by another entity, event, or factor.
-
B.
deathApprox
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
-
C.
deathDescribedBy
Indicates that a death event is documented, characterized, or explained by a specific description or source.
-
D.
deathOvers
Indicates the number of overs bowled in the final phase of a limited-overs cricket innings, typically focused on the closing overs where scoring and wicket-taking intensify.
-
E.
deathOutcome
Indicates that an event, condition, or action results in the death of the affected entity.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fcab6d41a88190a3576b4b088dcabd |
completed | May 7, 2026, 3:10 p.m. |
Created at: May 3, 2026, 4:17 p.m.