Triple
T25906813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | It Runs in the Family |
E652771
|
entity |
| Predicate | hasFamilyConnectionInCast |
P124291
|
FINISHED |
| Object | Douglas family |
—
|
NE NERFINISHED |
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: Douglas family | Statement: [It Runs in the Family, hasFamilyConnectionInCast, Douglas family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyConnectionInCast Context triple: [It Runs in the Family, hasFamilyConnectionInCast, Douglas family]
-
A.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
B.
isFromFamilyKnownFor
Indicates that an entity belongs to a family that is widely recognized or notable for a particular characteristic, achievement, or reputation.
-
C.
hasRelativeInCastOrCrew
chosen
Indicates that at least one member of a work’s cast or crew is a relative of a specified person.
-
D.
hasProtagonistFamilyMember
Indicates that a work’s protagonist has a specified individual as a member of their family.
-
E.
hasFamilyConnectionOutOfUniverse
Indicates that one entity has a familial relationship to another entity in a context external to the primary or canonical universe.
- 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_69e7ab3d3f8481909bc53ed64c06af33 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 22, 2026, 8:27 a.m.