Triple
T27499117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doctor Thorne |
E694098
|
entity |
| Predicate | protectsSecretRegarding |
P22701
|
FINISHED |
| Object | Mary Thorne’s parentage |
—
|
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: Mary Thorne’s parentage | Statement: [Doctor Thorne, protectsSecretRegarding, Mary Thorne’s parentage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectsSecretRegarding Context triple: [Doctor Thorne, protectsSecretRegarding, Mary Thorne’s parentage]
-
A.
keepsSecretAbout
chosen
Indicates that one entity intentionally withholds or conceals information regarding another specified entity or topic from others.
-
B.
confidentialityProtectedBy
Indicates that the confidentiality of some information is safeguarded or ensured by a specified protection mechanism, policy, or entity.
-
C.
keptPastSecretFrom
Indicates that one entity intentionally withheld or concealed information from another entity in the past.
-
D.
guardedSecretBy
Indicates that a secret is being protected or kept confidential by a specific entity.
-
E.
protectedFor
Indicates that something is safeguarded or preserved specifically for the benefit, use, or rights of a particular entity or purpose.
- 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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 1:10 p.m.