Triple
T23840999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amy Krouse Rosenthal |
E590986
|
entity |
| Predicate | wroteEssay |
P2831
|
FINISHED |
| Object | You May Want to Marry My Husband |
E1604553
|
NE 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: You May Want to Marry My Husband | Statement: [Amy Krouse Rosenthal, wroteEssay, You May Want to Marry My Husband]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wroteEssay Context triple: [Amy Krouse Rosenthal, wroteEssay, You May Want to Marry My Husband]
-
A.
wrote
chosen
Indicates that an entity is the author or creator of a written work involving another entity.
-
B.
containsEssay
Indicates that one entity includes or holds an essay as part of its contents.
-
C.
containsEssayBy
Indicates that one entity (such as a collection, volume, or publication) includes an essay authored by another specified entity.
-
D.
wroteIn
Indicates that an entity authored or composed something using a particular language, medium, or writing system.
-
E.
notableEssay
Indicates that an entity is the author or creator of an essay that is particularly significant, influential, or well-known.
- F. None of above.
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_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c88797d4819081831fd3f8822ef4 |
completed | April 29, 2026, 8:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0f7616779881909a2242b5f82828fe |
completed | May 21, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 8:08 p.m.