Triple
T29575981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Genius in the Family |
E753442
|
entity |
| Predicate | workBasedOnRealEvents |
P93832
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [A Genius in the Family, workBasedOnRealEvents, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workBasedOnRealEvents Context triple: [A Genius in the Family, workBasedOnRealEvents, true]
-
A.
basedOnRealLife
chosen
Indicates that something is derived from, inspired by, or directly adapted from actual real-world events, people, or situations.
-
B.
usesRealHistoricalEvents
Indicates that the subject incorporates or is based on actual events that occurred in real history.
-
C.
historicalWork
Indicates that one entity is a work (such as a document, artifact, or creation) that originates from or pertains to a past historical period in relation to another entity.
-
D.
workBasedOnFilm
Indicates that a creative work is derived from, adapted from, or otherwise based on a particular film.
-
E.
worksOnStoryAbout
Indicates that one entity is actively engaged in creating, developing, or contributing to a story whose subject or focus is another entity.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66d4a69048190973e14fe6bce5c7f |
completed | May 2, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:03 p.m.