Triple
T35042461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ripley 8 |
E1011103
|
entity |
| Predicate | cloneNumber |
P182041
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [Ripley 8, cloneNumber, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cloneNumber Context triple: [Ripley 8, cloneNumber, 8]
-
A.
cloneGeneration
Indicates the creation of a new entity as an exact or near-exact copy (clone) of an existing entity.
-
B.
copyNumberEffect
Indicates that a change in the number of copies of a genomic region (e.g., amplification or deletion) has a functional impact on a biological feature, such as gene expression or cellular behavior.
-
C.
cloneLine
Indicates that one line is a duplicate or exact copy of another line.
-
D.
cloneProject
Indicates creating an exact copy of an existing project, preserving its structure and content as a new, separate instance.
-
E.
cloneCommander
Indicates that one entity serves as the commanding officer or leader of a clone (or group of clones), holding authority and responsibility over them.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7865578d48190bf90e470634fd97d |
completed | May 3, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f78575917481909a3defd6a4c366bd |
completed | May 3, 2026, 5:27 p.m. |
Created at: May 3, 2026, 4:01 p.m.