Triple
T8255193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Spike ceremony |
E193053
|
entity |
| Predicate | telegraphMessageSent |
P58685
|
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: [Golden Spike ceremony, telegraphMessageSent, DONE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: telegraphMessageSent Context triple: [Golden Spike ceremony, telegraphMessageSent, DONE]
-
A.
sentSignalFrom
Indicates that one entity transmitted or emitted a signal originating from a specified source entity.
-
B.
sentSignalTo
chosen
Indicates that one entity transmitted a signal or message to another entity.
-
C.
sentAs
Indicates that one entity was transmitted, dispatched, or delivered in the form, role, or capacity of another (e.g., an item or message being sent as something specific).
-
D.
sentMessengersTo
Indicates that one entity dispatched or directed messengers to another entity or location for communication or representation.
-
E.
sentTeamTo
Indicates that one entity dispatched or assigned a team to go to or operate at another entity or location.
- 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_69ca82dfad9c8190b8cd18fb89f50f40 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78f9f680819088f1d56e0f98974f |
completed | March 31, 2026, 7:34 a.m. |
| PD | Predicate disambiguation | batch_69cb36b6d5548190b665a6cce14c69f7 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.