Triple
T17825746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William of Apulia |
E445112
|
entity |
| Predicate | workCompletedAfter |
P129343
|
FINISHED |
| Object | Robert Guiscard’s death |
—
|
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: Robert Guiscard’s death | Statement: [William of Apulia, workCompletedAfter, Robert Guiscard’s death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workCompletedAfter Context triple: [William of Apulia, workCompletedAfter, Robert Guiscard’s death]
-
A.
completedBy
Indicates that a task, process, or action has been finished or carried out by a particular entity.
-
B.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
C.
alsoCompletedBy
Indicates that the same task, activity, or item has been completed by an additional agent or entity besides the one already referenced.
-
D.
completedBefore
Indicates that one event or action was fully completed prior to the start or completion of another specified event or action.
-
E.
workAfter
Indicates that one entity performs its work or begins an activity only after another specified entity has completed or started its own work.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48914226c819083edcc78e00b2d42 |
completed | April 19, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3f022ec448190a9bf191be1c5f570 |
completed | April 18, 2026, 8:57 p.m. |
Created at: April 10, 2026, 10:15 a.m.