Triple
T14712223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bedevere |
E345575
|
entity |
| Predicate | hesitatesTo |
P115469
|
FINISHED |
| Object | throw Excalibur into the lake |
—
|
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: throw Excalibur into the lake | Statement: [Bedevere, hesitatesTo, throw Excalibur into the lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hesitatesTo Context triple: [Bedevere, hesitatesTo, throw Excalibur into the lake]
-
A.
intendsTo
Indicates that one entity has the purpose, plan, or desire to perform an action involving another entity or outcome.
-
B.
heldFrom
Indicates that an entity is held, possessed, or occupied starting from a specified point in time.
-
C.
halted
Indicates that an ongoing process, action, or movement has been stopped or brought to an end.
-
D.
mayDelay
Indicates that one entity has the potential or permission to cause a postponement or slowing of another entity, event, or process.
-
E.
refusesHelpFrom
Indicates that one entity declines or rejects assistance offered by another entity.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb982bf248190881e21a8a0861a3f |
completed | April 14, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69de657c57ec8190ae0b9bb79a514566 |
completed | April 14, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69de716d3aac8190aaa6dc1f099b86e8 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:28 a.m.