Triple
T6515188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaplin family |
E148238
|
entity |
| Predicate | multiGenerational |
P52584
|
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: [Chaplin family, multiGenerational, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: multiGenerational Context triple: [Chaplin family, multiGenerational, true]
-
A.
multiGenerationControl
Indicates a relationship where one entity exercises control or influence over multiple successive generations of another entity or group.
-
B.
multiGenerationOwnershipOf
Indicates that ownership of something extends across multiple generations within the same family or lineage.
-
C.
hasGenerations
chosen
Indicates a relationship where an entity is associated with one or more successive generational levels or cohorts derived from it.
-
D.
secondGeneration
Indicates that one entity belongs to the second generation relative to another, such as being the child of a first-generation member in a lineage or sequence.
-
E.
finalGenerationOf
Indicates that one entity represents the last or ultimate generation or iteration in a sequence or lineage of 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ac0bea808190aebc2905fb53eeba |
completed | March 27, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69c68ab98c78819081743e614df04e1d |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:44 p.m.