Triple
T8545241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolly Talbo |
E202303
|
entity |
| Predicate | keepsSecret |
P22701
|
FINISHED |
| Object | formula for a dropsy medicine |
—
|
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: formula for a dropsy medicine | Statement: [Dolly Talbo, keepsSecret, formula for a dropsy medicine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keepsSecret Context triple: [Dolly Talbo, keepsSecret, formula for a dropsy medicine]
-
A.
keepsSecretAbout
chosen
Indicates that one entity intentionally withholds or conceals information regarding another specified entity or topic from others.
-
B.
secretes
Indicates that one entity produces and releases a substance from within itself into its surrounding environment or another entity.
-
C.
secretive
Indicates that an entity deliberately withholds information or conceals its thoughts, actions, or intentions from others.
-
D.
knowsSecret
Indicates that one entity is aware of confidential or hidden information about another entity or situation.
-
E.
confidantOf
Indicates a relationship in which one entity is trusted by another to receive and keep personal, private, or sensitive information.
- 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_69ca832461e88190a654c5e44e233aa8 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6e4e21c8190afcbca73713a5fa8 |
completed | March 31, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69cbd113e05c81908f4f3fc1b5925164 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:18 p.m.