Triple
T26701188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morgan Freeman as Ned Logan |
E673158
|
entity |
| Predicate | bodyDisplayedAsWarningBy |
P161136
|
FINISHED |
| Object | Little Bill Daggett |
—
|
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: Little Bill Daggett | Statement: [Morgan Freeman as Ned Logan, bodyDisplayedAsWarningBy, Little Bill Daggett]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyDisplayedAsWarningBy Context triple: [Morgan Freeman as Ned Logan, bodyDisplayedAsWarningBy, Little Bill Daggett]
-
A.
warningGivenBy
Indicates that one entity issues or delivers a warning to another entity.
-
B.
warningIssued
Indicates that a formal warning or alert has been communicated from one entity to another regarding a potential or existing risk, problem, or violation.
-
C.
warnsAbout
Indicates that one entity alerts or cautions another entity about a potential danger, risk, or problem.
-
D.
causeOfWarning
Indicates that one entity is the reason or source that triggers a warning about another entity or situation.
-
E.
warningIncludes
Indicates that a warning message or notice contains or encompasses specific information, elements, or details.
- 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_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6177ef08481908130a8cc2ec33fb2 |
completed | May 2, 2026, 3:25 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, 3:31 a.m.