Triple

T14494079
Position Surface form Disambiguated ID Type / Status
Subject Hôtel-Dieu de Tonnerre E359442 entity
Predicate hasFunctionHistory P2715 FINISHED
Object hospital until the 20th century 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: hospital until the 20th century | Statement: [Hôtel-Dieu de Tonnerre, hasFunctionHistory, hospital until the 20th century]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFunctionHistory
Context triple: [Hôtel-Dieu de Tonnerre, hasFunctionHistory, hospital until the 20th century]
  • A. hasScriptHistory
    Indicates that an entity is associated with a record or chronology of scripts or writing systems it has used or been represented in over time.
  • B. historicalFunction chosen
    Indicates the role, purpose, or activity an entity had during a past period or in a historical context.
  • C. hasHistoryIn
    Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
  • D. hasResourceHistory
    Indicates that an entity is associated with a record or sequence of past states, usages, or changes of a particular resource over time.
  • E. hasFlagHistory
    Indicates that there exists a historical record or sequence of changes related to an entity’s flag.
  • 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_69d8279740308190af9df93a3af8592e completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de930f34d08190b4b30e54e2f702ed completed April 14, 2026, 7:18 p.m.
PD Predicate disambiguation batch_69de5c4ccba08190a988bfda0bc9f5cb completed April 14, 2026, 3:25 p.m.
Created at: April 10, 2026, 1:21 a.m.