Triple

T5547050
Position Surface form Disambiguated ID Type / Status
Subject The Gambler E145433 entity
Predicate writtenUnderConstraint P65305 FINISHED
Object tight deadline due to publishing contract 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: tight deadline due to publishing contract | Statement: [The Gambler, writtenUnderConstraint, tight deadline due to publishing contract]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: writtenUnderConstraint
Context triple: [The Gambler, writtenUnderConstraint, tight deadline due to publishing contract]
  • A. writtenIn
    Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
  • B. writtenDuring
    Indicates that the creation or authorship of something took place within a specified time period or historical event.
  • C. wroteIn
    Indicates that an entity authored or composed something using a particular language, medium, or writing system.
  • D. written
    Indicates that one entity has created or authored a text, document, or written work involving or about another entity.
  • E. designedToConstrain
    Indicates that one entity is intentionally created or configured to limit, restrict, or control the behavior, range, or properties of another entity.
  • 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_69c008fb879c81909f5bfa56fadc1d46 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c01fdec3588190b0af7d2ca8e8ee9b completed March 22, 2026, 4:59 p.m.
PD Predicate disambiguation batch_69c01b0e72f08190bf705d8fe1639401 completed March 22, 2026, 4:38 p.m.
PDg Predicate description generation batch_69c01f051e508190b3886d87b4afdd0b completed March 22, 2026, 4:55 p.m.
Created at: March 22, 2026, 3:35 p.m.