Triple
T32871854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege Perilous |
E840813
|
entity |
| Predicate | ultimatelyFilledBy |
P175538
|
FINISHED |
| Object | Sir Galahad |
—
|
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: Sir Galahad | Statement: [Siege Perilous, ultimatelyFilledBy, Sir Galahad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ultimatelyFilledBy Context triple: [Siege Perilous, ultimatelyFilledBy, Sir Galahad]
-
A.
mayBeFilledBy
Indicates that one entity has the potential or permission to be occupied, completed, or satisfied by another entity.
-
B.
saidToBeFulfilledBy
Indicates that a requirement, condition, or expectation is claimed or considered to be satisfied by a particular entity or action.
-
C.
isTypicallyFilledWith
Indicates that one entity is commonly or usually occupied, loaded, or contained by another entity.
-
D.
formedBy
Indicates that something comes into existence or is created as a result of a specific agent, process, or combination of components.
-
E.
termFilled
Indicates that a specific term, field, or placeholder has been completed or populated with a value.
- 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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d210fc80819091ed8961aa2cddfb |
completed | May 3, 2026, 4:41 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d16b79dc8190ab0d4657f2ef9a5b |
completed | May 3, 2026, 4:39 a.m. |
Created at: May 1, 2026, 1:17 a.m.