Triple

T14846056
Position Surface form Disambiguated ID Type / Status
Subject League of Nations records E349089 entity
Predicate provideEvidenceFor P3650 FINISHED
Object work of the League of Nations 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: work of the League of Nations | Statement: [League of Nations records, provideEvidenceFor, work of the League of Nations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: provideEvidenceFor
Context triple: [League of Nations records, provideEvidenceFor, work of the League of Nations]
  • A. providesEvidenceFor chosen
    Indicates that one entity serves as support, justification, or proof for the validity or truth of another entity.
  • B. usedEvidenceType
    Indicates that a particular type or category of evidence was employed or relied upon in a given context or activity.
  • C. hasMaterialEvidence
    Indicates that there exists tangible, physical evidence supporting or associated with a particular entity, event, or claim.
  • D. stanceOnProofs
    Indicates the position or attitude an entity holds regarding the use, value, or nature of proofs.
  • E. mayHearEvidenceFrom
    Indicates that an authority or decision-maker is permitted to receive and consider evidence presented by a specified source.
  • 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_69d822ec69008190a9232caa68836872 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69ded29236dc8190b7d3a37d09f9fb21 completed April 14, 2026, 11:49 p.m.
PD Predicate disambiguation batch_69de8c13418c819088ff9905ace1416a completed April 14, 2026, 6:48 p.m.
Created at: April 10, 2026, 1:53 a.m.