Triple
T33121637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Not Penny's Boat |
E847616
|
entity |
| Predicate | warnsThat |
P2399
|
FINISHED |
| Object | the freighter is dangerous |
—
|
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: the freighter is dangerous | Statement: [Not Penny's Boat, warnsThat, the freighter is dangerous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warnsThat Context triple: [Not Penny's Boat, warnsThat, the freighter is dangerous]
-
A.
warnsAbout
chosen
Indicates that one entity alerts or cautions another entity about a potential danger, risk, or problem.
-
B.
warnsAboutAction
Indicates that one entity alerts another about a potential or impending action, typically to caution or prevent negative consequences.
-
C.
warnedWith
Indicates that one entity issued a warning to another entity using or accompanied by a particular medium, content, or instrument.
-
D.
warningIncludes
Indicates that a warning message or notice contains or encompasses specific information, elements, or details.
-
E.
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.
- 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d71a52288190bfdbb5c1913a7787 |
completed | May 3, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69f6d27224708190b31a541cebe0ff77 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:27 a.m.