Triple

T20375437
Position Surface form Disambiguated ID Type / Status
Subject Donny & Marie E497678 entity
Predicate runDuration P43134 FINISHED
Object approximately 11 years 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: approximately 11 years | Statement: [Donny & Marie, runDuration, approximately 11 years]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: runDuration
Context triple: [Donny & Marie, runDuration, approximately 11 years]
  • A. runsFor
    Indicates that an entity performs a running activity on behalf of, or as a representative of, another entity (such as a team, organization, or cause).
  • B. runtimeMinutes
    Indicates the total duration of something, typically a media work or process, measured in minutes.
  • C. 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.
  • D. durationTotal chosen
    Indicates the overall length of time for which an event, process, or state persists, typically aggregating all its constituent durations.
  • E. actualDuration
    Indicates the real amount of time that an event, process, or activity actually took to complete, as opposed to its planned or estimated duration.
  • 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_69e0b4a5b7908190a972e4e7e698ae94 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e678acae3c8190ae04323760bf5597 completed April 20, 2026, 7:04 p.m.
PD Predicate disambiguation batch_69e57648be3c81908256838228cabf5c completed April 20, 2026, 12:41 a.m.
Created at: April 16, 2026, 11:27 a.m.