Triple

T25368364
Position Surface form Disambiguated ID Type / Status
Subject Tokyo 2020 Olympic venues E632863 entity
Predicate originalPlannedTimePeriod P4691 FINISHED
Object 2020 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: 2020 | Statement: [Tokyo 2020 Olympic venues, originalPlannedTimePeriod, 2020]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: originalPlannedTimePeriod
Context triple: [Tokyo 2020 Olympic venues, originalPlannedTimePeriod, 2020]
  • A. originallyPlannedFor
    Indicates that something was initially intended, designed, or scheduled to be used for or associated with a particular purpose, event, or entity, regardless of what ultimately occurred.
  • B. plannedAt
    Indicates that an event, action, or activity is scheduled or intended to occur at a specific time or date.
  • C. plannedFrom
    Indicates that something is scheduled or arranged to originate, start, or be derived from a specified source, time, or condition.
  • D. datePlanned chosen
    Indicates that a specific date has been scheduled or intended for a particular event, action, or relationship to occur.
  • E. plannedAgainst
    Indicates that an entity has formulated or coordinated plans targeting another entity, typically with opposing or adversarial intent.
  • 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_69e75a90c0dc819092f928b6ea0ecc72 completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f7117e55908190a67105e92bc4830f completed May 3, 2026, 9:12 a.m.
PD Predicate disambiguation batch_69f70f380690819090cc34763ba460ed completed May 3, 2026, 9:02 a.m.
Created at: April 21, 2026, 1:38 p.m.