Triple
T33121639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Not Penny's Boat |
E847616
|
entity |
| Predicate | warnsCharacters |
P176120
|
FINISHED |
| Object | Desmond Hume |
—
|
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: Desmond Hume | Statement: [Not Penny's Boat, warnsCharacters, Desmond Hume]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warnsCharacters Context triple: [Not Penny's Boat, warnsCharacters, Desmond Hume]
-
A.
warnsAbout
Indicates that one entity alerts or cautions another entity about a potential danger, risk, or problem.
-
B.
hasCharacters
Indicates that an entity (such as a work or story) includes or features certain characters as part of its content.
-
C.
usesCharactersAs
Indicates that one entity employs or incorporates specific characters (such as letters, symbols, or glyphs) from another entity for its representation or functioning.
-
D.
warningIncludes
Indicates that a warning message or notice contains or encompasses specific information, elements, or details.
-
E.
capturesCharacter
Indicates that one entity seizes, traps, or takes control of another character.
- 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db6a38d881909ecc75cc527910f2 |
completed | May 3, 2026, 5:21 a.m. |
Created at: May 1, 2026, 1:27 a.m.