Triple

T22975683
Position Surface form Disambiguated ID Type / Status
Subject Fargo (1996 film) E571308 entity
Predicate basedOnClaim P7125 FINISHED
Object inspired by true events (fictionalized) 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: inspired by true events (fictionalized) | Statement: [Fargo (1996 film), basedOnClaim, inspired by true events (fictionalized)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: basedOnClaim
Context triple: [Fargo (1996 film), basedOnClaim, inspired by true events (fictionalized)]
  • A. basedOnBy
    Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
  • B. basedOnFactFrom
    Indicates that something is derived, justified, or constructed using factual information obtained from a specified source.
  • C. hasClaimOn
    Indicates that one entity holds a right, entitlement, or demand over another entity or its resources.
  • D. areBasedOn
    Indicates that one entity is founded, derived, or developed from the principles, content, or structure of another entity.
  • E. isBasedOn chosen
    Indicates that one entity is derived from, inspired by, or developed using the content, structure, or principles 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_69e245b2c6548190a0e4c7f2f7df2d48 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18235de508190ab9675d005870ff6 completed April 29, 2026, 3:59 a.m.
PD Predicate disambiguation batch_69ef3b9101f48190a06c69dff26c6441 completed April 27, 2026, 10:33 a.m.
Created at: April 17, 2026, 3:48 p.m.