Triple
T36571806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond |
E902138
|
entity |
| Predicate | finalSpeechFunction |
P198329
|
FINISHED |
| Object | promises peace and reconciliation |
—
|
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: promises peace and reconciliation | Statement: [Richmond, finalSpeechFunction, promises peace and reconciliation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalSpeechFunction Context triple: [Richmond, finalSpeechFunction, promises peace and reconciliation]
-
A.
givesSpeechOn
Indicates that one entity delivers or presents a speech whose topic or subject matter concerns another entity.
-
B.
givesSpeechTo
Indicates that one entity delivers a speech or formal address directed toward another entity or audience.
-
C.
givesSpeechIn
Indicates that an entity delivers or presents a speech within a particular location, event, or context.
-
D.
finalService
Indicates that a service represents the last or concluding service in a sequence, process, or lifecycle.
-
E.
functionInRecital
Indicates that an entity performs or participates in a musical or artistic function within a recital event.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fedd5a5f4c8190acce88db56303703 |
completed | May 9, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69fed910b31c8190ae837163d146738d |
completed | May 9, 2026, 6:49 a.m. |
| PDg | Predicate description generation | batch_69fedd5915588190bd884054e4be0414 |
completed | May 9, 2026, 7:08 a.m. |
Created at: May 3, 2026, 4:11 p.m.