Triple
T3287836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bedivere |
E69025
|
entity |
| Predicate | initiallyRefuses |
P19799
|
FINISHED |
| Object | to throw Excalibur away |
—
|
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: to throw Excalibur away | Statement: [Bedivere, initiallyRefuses, to throw Excalibur away]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initiallyRefuses Context triple: [Bedivere, initiallyRefuses, to throw Excalibur away]
-
A.
rarelyRefused
Indicates that an action, request, or offer is almost always accepted and only infrequently declined.
-
B.
typicallyDenies
chosen
Indicates that an entity, in most usual or common circumstances, refuses, rejects, or does not grant something to another entity.
-
C.
rejectedBy
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
-
D.
rejectedBecause
Indicates that one entity refused, dismissed, or did not accept another entity specifically due to a stated reason or cause.
-
E.
mayReject
Indicates that one entity has the authority or option to refuse, decline, or not accept another entity or proposal.
- 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_69ad859d45748190b0742408c954b39f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb058e00881908fdf0a23208860d4 |
completed | March 8, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69ada421fadc8190b7c7d3c8afd20061 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.