Triple

T29059227
Position Surface form Disambiguated ID Type / Status
Subject Prussian Field Army under Gebhard Leberecht von Blücher E735477 entity
Predicate arrivalAtWaterloo P49364 FINISHED
Object afternoon and evening of 18 June 1815 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: afternoon and evening of 18 June 1815 | Statement: [Prussian Field Army under Gebhard Leberecht von Blücher, arrivalAtWaterloo, afternoon and evening of 18 June 1815]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: arrivalAtWaterloo
Context triple: [Prussian Field Army under Gebhard Leberecht von Blücher, arrivalAtWaterloo, afternoon and evening of 18 June 1815]
  • A. arrivalAt chosen
    Indicates the event or state of an entity reaching and being present at a specific destination or location.
  • B. departureTime
    Indicates the specific time at which an entity leaves or begins its departure from a location or state.
  • C. arrivalTimePattern
    Indicates a recurring or structured pattern in the times at which an entity arrives.
  • D. arrivalRelatedTo
    Indicates that an arrival event is connected or associated with another entity, event, or circumstance.
  • E. estimatedArrivalInAustralia
    Indicates the expected date and/or time when an entity is predicted to arrive in Australia.
  • 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_69f077e85498819088b65186550da8cd completed April 28, 2026, 9:03 a.m.
NER Named-entity recognition batch_69f66095794c81909288f4255c47923f completed May 2, 2026, 8:37 p.m.
PD Predicate disambiguation batch_69f659d297cc8190b2b962ba30a1edb3 completed May 2, 2026, 8:08 p.m.
Created at: April 28, 2026, 10:14 a.m.