Triple
T25427398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clavius |
E637150
|
entity |
| Predicate | primaryTaskInPlot |
P88311
|
FINISHED |
| Object | locate the missing body of Jesus |
—
|
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: locate the missing body of Jesus | Statement: [Clavius, primaryTaskInPlot, locate the missing body of Jesus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTaskInPlot Context triple: [Clavius, primaryTaskInPlot, locate the missing body of Jesus]
-
A.
taskInPlot
Indicates that a specific task occurs within, is associated with, or is part of a particular plot or storyline.
-
B.
primaryTask
Indicates that an entity has a main or most important task, role, or function it is responsible for above all others.
-
C.
primaryFunctionInPlot
chosen
Indicates the main narrative role or purpose that an entity serves within the plot of a story.
-
D.
partOfPlot
Indicates that one event, action, or element is a constituent component within the overall plot of a narrative.
-
E.
hasMainPlotElement
Indicates that one entity serves as a central or primary plot element within the narrative 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 21, 2026, 1:57 p.m.