Triple

T15923715
Position Surface form Disambiguated ID Type / Status
Subject Mille Miglia E386153 entity
Predicate resumedAs P57058 FINISHED
Object historic regularity rally 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: historic regularity rally | Statement: [Mille Miglia, resumedAs, historic regularity rally]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: resumedAs
Context triple: [Mille Miglia, resumedAs, historic regularity rally]
  • A. resumedIn
    Indicates that an activity, process, or state that was previously paused or interrupted has started again within or at a specified context, time, or location.
  • B. resumesAfter
    Indicates that an activity, process, or state starts again following a pause, interruption, or completion of another specified event.
  • C. revivedAs chosen
    Indicates that an entity, after having ceased to exist or function in its original form, comes back into existence or operation in a new or restored form.
  • D. resumedCouncil
    Indicates that a council or formal deliberative body has restarted its meetings or proceedings after a pause or interruption.
  • E. reemergesAs
    Indicates that an entity that previously disappeared, transformed, or became inactive later appears again in a new or altered form.
  • 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_69d86da750008190987eb26be3f6c118 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e172b48b308190bc430b2308cbc75b completed April 16, 2026, 11:37 p.m.
PD Predicate disambiguation batch_69e142cf5c548190a931f7b58144cd31 completed April 16, 2026, 8:13 p.m.
Created at: April 10, 2026, 4:52 a.m.