Triple
T37353103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jon & Kate Plus 8 |
E927377
|
entity |
| Predicate | featuresTwins |
—
|
GENERATED |
| Object | yes |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresTwins Context triple: [Jon & Kate Plus 8, featuresTwins, yes]
-
A.
twinType
Indicates that one entity is classified as a specific type or category of twin in relation to another entity.
-
B.
hasTwinFeature
Indicates that two entities share an identical or nearly identical feature, characteristic, or component, as if they are twins in that respect.
-
C.
hasTwin
Indicates that one entity is a twin of another, sharing the same birth event or time with a sibling.
-
D.
twinning
Indicates that two entities are paired or linked as twins, typically sharing a formally recognized, parallel, or closely matched relationship.
-
E.
featuresDoubleAct
Indicates that an entity includes or presents a performance, show, or act involving two main performers acting together as a pair.
- F. None of above. chosen
Provenance (1 batch)
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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.