Triple
T37353103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jon & Kate Plus 8 |
E927377
|
entity |
| Predicate | featuresTwins |
P205848
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Jon & Kate Plus 8, featuresTwins, yes]
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 (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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:16 p.m.