Triple
T20118845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Take a Message to Mary |
E490541
|
entity |
| Predicate | asksToConvey |
P138755
|
FINISHED |
| Object | that he has found another love |
—
|
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: that he has found another love | Statement: [Take a Message to Mary, asksToConvey, that he has found another love]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: asksToConvey Context triple: [Take a Message to Mary, asksToConvey, that he has found another love]
-
A.
asksToDescribe
Indicates that one entity requests another entity to provide a description or explanation of something.
-
B.
questionConveyedBy
Indicates that a particular question is expressed, communicated, or represented by a given medium, message, or artifact.
-
C.
asksToMarry
Indicates that one entity proposes marriage to another, requesting that they become spouses.
-
D.
asksToInvestigate
Indicates that one entity requests another entity to carry out an investigation into something.
-
E.
intendsTo
Indicates that one entity has the purpose, plan, or desire to perform an action involving another entity or outcome.
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6673c32bc8190a52875961fbcc5e2 |
completed | April 20, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc2bc3c819088c33cd263303433 |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 11:30 p.m.