Triple

T36142855
Position Surface form Disambiguated ID Type / Status
Subject Gaston Doumergue E1045360 entity
Predicate recalledToOffice P184746 FINISHED
Object 1934-02-09 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: 1934-02-09 | Statement: [Gaston Doumergue, recalledToOffice, 1934-02-09]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: recalledToOffice
Context triple: [Gaston Doumergue, recalledToOffice, 1934-02-09]
  • A. recalledFromOffice
    Indicates that an entity has been officially summoned or brought back from its office or post, typically ending or interrupting its assignment there.
  • B. recalledIn
    Indicates that an entity is mentioned, remembered, or brought up again within a specific context, such as a document, conversation, or event.
  • C. recalledBy
    Indicates that an entity is brought back, retrieved, or remembered as a result of another entity’s action or prompting.
  • D. isRecallOf
    Indicates that one event, statement, or action serves as a recall, retrieval, or re-mention of a previously occurring or stated event, statement, or action.
  • E. forcedToReturnTo
    Indicates that one entity is compelled, against its preference or by external pressure or requirement, to go back to a previous place, state, or situation.
  • F. None of above. chosen

Provenance (4 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_69f76e37ace88190a906b107d388f5d1 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7b3e2f3c08190be4fd1ae4fa1266d completed May 3, 2026, 8:45 p.m.
PD Predicate disambiguation batch_69f7b1bcc47081909fe7d592ac69006c completed May 3, 2026, 8:36 p.m.
PDg Predicate description generation batch_69f7b3e0f1c88190985feab6cee8b05e completed May 3, 2026, 8:45 p.m.
Created at: May 3, 2026, 4:08 p.m.