Triple
T11404716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sam Evans |
E270206
|
entity |
| Predicate | familySecretInvolves |
P99129
|
FINISHED |
| Object | hereditary insanity |
—
|
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: hereditary insanity | Statement: [Sam Evans, familySecretInvolves, hereditary insanity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familySecretInvolves Context triple: [Sam Evans, familySecretInvolves, hereditary insanity]
-
A.
keepsSecretAbout
Indicates that one entity intentionally withholds or conceals information regarding another specified entity or topic from others.
-
B.
revealedSecretOf
Indicates that one entity has disclosed or exposed confidential or previously unknown information belonging to another entity.
-
C.
secretes
Indicates that one entity produces and releases a substance from within itself into its surrounding environment or another entity.
-
D.
secretAffiliation
Indicates a hidden or undisclosed association, membership, or allegiance that one entity has with another.
-
E.
knowsSecret
Indicates that one entity is aware of confidential or hidden information about another entity or situation.
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8014ab46881909fa1d425926c617b |
completed | April 9, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69d7e70ffd708190b62a78ebcbce9f78 |
completed | April 9, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69d80010712c819089ea2e31e664abe1 |
completed | April 9, 2026, 7:37 p.m. |
Created at: April 8, 2026, 9:34 p.m.