Triple
T30396596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Susanna Dickinson |
E773234
|
entity |
| Predicate | conveyedMessageTo |
P40250
|
FINISHED |
| Object | Sam Houston |
—
|
NE NERFINISHED |
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: Sam Houston | Statement: [Susanna Dickinson, conveyedMessageTo, Sam Houston]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conveyedMessageTo Context triple: [Susanna Dickinson, conveyedMessageTo, Sam Houston]
-
A.
intendedMessage
Indicates that one entity is the message or content that another entity aims or plans to communicate.
-
B.
communicatesTo
chosen
Indicates that one entity sends or conveys information, messages, or signals to another entity as the intended recipient.
-
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.
mailedTo
Indicates that something was sent or delivered by mail from one entity to another as the recipient.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 29, 2026, 8:02 p.m.