Triple

T14706283
Position Surface form Disambiguated ID Type / Status
Subject Battle of the Bastards E345437 entity
Predicate approximateRuntimeMinutes P1958 FINISHED
Object 60 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: 60 | Statement: [Battle of the Bastards, approximateRuntimeMinutes, 60]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: approximateRuntimeMinutes
Context triple: [Battle of the Bastards, approximateRuntimeMinutes, 60]
  • A. runtimeMinutes chosen
    Indicates the total duration of something, typically a media work or process, measured in minutes.
  • B. runsApproximately
    Indicates that an entity performs a running action in a manner that is close to, but not exactly matching, a specified time, distance, speed, or other running-related measure.
  • C. endTimeApproximate
    Indicates that the recorded end time of an event or action is not exact but an approximate value.
  • D. timeToComplete
    Indicates the duration required for an entity or process to be fully completed.
  • E. intendedDuration
    Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
  • 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_69d822e4a8c08190a155df736bb7bc13 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb6086c608190a66c64e23a3e002f completed April 14, 2026, 9:47 p.m.
PD Predicate disambiguation batch_69de657c57ec8190ae0b9bb79a514566 completed April 14, 2026, 4:04 p.m.
Created at: April 10, 2026, 1:28 a.m.