Triple
T16141441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | wizard of Alderley Edge |
E391663
|
entity |
| Predicate | awaitsEvent |
P106933
|
FINISHED |
| Object | time of great need |
—
|
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: time of great need | Statement: [wizard of Alderley Edge, awaitsEvent, time of great need]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awaitsEvent Context triple: [wizard of Alderley Edge, awaitsEvent, time of great need]
-
A.
expectsEvent
chosen
Indicates that one entity anticipates, awaits, or is scheduled to receive the occurrence of a specific event.
-
B.
attendsTo
Indicates that one entity directs care, attention, or service toward another entity or task.
-
C.
awaited
Indicates that one entity is expected or looked forward to by another, typically involving a period of waiting for its arrival, occurrence, or response.
-
D.
eventuallyIn
Indicates that one entity will, at some later time or in the long run, come to be located in, belong to, or be contained within another entity or state.
-
E.
captureEvent
Indicates an event in which one entity successfully takes control, possession, or custody of another entity.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21a087c848190aba9ed2ccb422427 |
completed | April 17, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.