Triple

T17021184
Position Surface form Disambiguated ID Type / Status
Subject Supplementum E412949 entity
Predicate intendedToComplete P88492 FINISHED
Object unfinished sections of the Summa Theologiae 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: unfinished sections of the Summa Theologiae | Statement: [Supplementum, intendedToComplete, unfinished sections of the Summa Theologiae]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: intendedToComplete
Context triple: [Supplementum, intendedToComplete, unfinished sections of the Summa Theologiae]
  • A. intendsTo chosen
    Indicates that one entity has the purpose, plan, or desire to perform an action involving another entity or outcome.
  • B. completedIn
    Indicates that an action, process, or task was fully finished within a specified time period or duration.
  • C. intendedWith
    Indicates that one entity is the planned or desired target, recipient, or context for the use or application of another entity.
  • D. isComplete
    Indicates that an action, process, or object has finished all required steps or reached its final state with nothing remaining to be done.
  • E. completedBefore
    Indicates that one event or action was fully completed prior to the start or completion of another specified event or action.
  • 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_69d886cc4170819093deddc7b8b4b6a7 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d5d0dc848190a267f8542dfb86a6 completed April 18, 2026, 7:04 p.m.
PD Predicate disambiguation batch_69e35d5be7f48190af9db67a1e23850f completed April 18, 2026, 10:30 a.m.
Created at: April 10, 2026, 5:33 a.m.