Triple

T15886429
Position Surface form Disambiguated ID Type / Status
Subject get (Jewish bill of divorce) E385202 entity
Predicate mustBeWrittenWith P8571 FINISHED
Object intent for this particular couple 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: intent for this particular couple | Statement: [get (Jewish bill of divorce), mustBeWrittenWith, intent for this particular couple]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mustBeWrittenWith
Context triple: [get (Jewish bill of divorce), mustBeWrittenWith, intent for this particular couple]
  • A. willWrittenIn
    Indicates that a legal will was authored, drafted, or formally written in a specified location or jurisdiction.
  • B. isWritten
    Indicates that a text, document, or content has been created or recorded in written form by an agent.
  • C. likelyWrittenFrom
    Indicates that something (such as a text, statement, or perspective) is probably authored or expressed from the viewpoint, context, or position of a particular entity.
  • D. writtenTo
    Indicates that something has been addressed or directed in written form to a particular recipient.
  • E. usedToWrite chosen
    Indicates that one entity served as a tool, medium, or instrument that another entity employed to perform the act of writing.
  • 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_69d86da5b800819083a31be937d738b0 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e174de2cd48190ab18e48c9f051a2a completed April 16, 2026, 11:46 p.m.
PD Predicate disambiguation batch_69e142c3e18c8190bb7b023f4a0eaebb completed April 16, 2026, 8:12 p.m.
Created at: April 10, 2026, 4:51 a.m.