Triple

T28495185
Position Surface form Disambiguated ID Type / Status
Subject Driving of the Last Spike E721088 entity
Predicate telegraphedAs P138485 FINISHED
Object DONE 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: DONE | Statement: [Driving of the Last Spike, telegraphedAs, DONE]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: telegraphedAs
Context triple: [Driving of the Last Spike, telegraphedAs, DONE]
  • A. telegraphInvolved
    Indicates that a telegraph was used as a means of communication or played a role in the described interaction or event between entities.
  • B. transmittedIn
    Indicates that something (such as information, a signal, or a disease) is passed or conveyed within or through a particular medium, environment, or context.
  • C. laterTransmittedAs chosen
    Indicates that some information, message, or content was transmitted or communicated at a later time as a particular form, version, or representation.
  • D. transcribedAs
    Indicates that one entity is a written or recorded representation of another entity’s content, typically converting it from one form (e.g., audio, handwriting) into text.
  • E. communicatedAs
    Indicates that one entity is expressed, conveyed, or presented in the form, manner, or role of another.
  • 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_69f01a5afdac8190ac6e72d5c100bd58 completed April 28, 2026, 2:24 a.m.
NER Named-entity recognition batch_69f64f3ed46c8190bf19437b134edcf7 completed May 2, 2026, 7:23 p.m.
PD Predicate disambiguation batch_69f64cb0d8008190912e1430cfaf92aa completed May 2, 2026, 7:12 p.m.
Created at: April 28, 2026, 3:03 a.m.