Triple
T29136386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tech |
E738520
|
entity |
| Predicate | cloneBatch |
P83994
|
FINISHED |
| Object | Clone Force 99 |
—
|
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: Clone Force 99 | Statement: [Tech, cloneBatch, Clone Force 99]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cloneBatch Context triple: [Tech, cloneBatch, Clone Force 99]
-
A.
cloneLine
Indicates that one line is a duplicate or exact copy of another line.
-
B.
cloneRelation
chosen
Indicates that one entity is a clone or exact copy derived from another entity.
-
C.
cloneStateIntroduced
Indicates that a particular state or condition was created or brought into existence as a result of a cloning process.
-
D.
copiesPrepared
Indicates that one entity has produced or made available a certain number of copies of another entity (such as a document, item, or resource).
-
E.
cloneCondition
Indicates that one entity is a duplicate or replication of another under the same specified conditions or parameters.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6626ac7508190959be92ac34c33ac |
completed | May 2, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 11:34 a.m.