Triple
T29149272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delphi |
E738857
|
entity |
| Predicate | triesToChangeEvent |
P28300
|
FINISHED |
| Object | Battle of Hogwarts |
—
|
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: Battle of Hogwarts | Statement: [Delphi, triesToChangeEvent, Battle of Hogwarts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triesToChangeEvent Context triple: [Delphi, triesToChangeEvent, Battle of Hogwarts]
-
A.
triesToSave
Indicates an entity is making an effort or taking action with the intention of rescuing or preserving another entity or situation from harm, loss, or failure.
-
B.
triesToUse
Indicates an entity’s attempt or effort to make use of another entity, regardless of whether the use is successful.
-
C.
triesToTake
Indicates an attempt by one entity to take possession or control of another entity or resource, regardless of whether the attempt succeeds.
-
D.
canTry
Indicates that an entity has the possibility or permission to attempt performing a particular action or achieving a certain outcome.
-
E.
seeksStatusChange
chosen
Indicates an entity’s intention or attempt to alter the current state, condition, or status of another entity or situation.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f662a362088190b474e822a96086e8 |
completed | May 2, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:41 a.m.