Triple
T29136458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omega |
E738522
|
entity |
| Predicate | cloneGeneration |
P166923
|
FINISHED |
| Object | unaltered clone |
—
|
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: unaltered clone | Statement: [Omega, cloneGeneration, unaltered clone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cloneGeneration Context triple: [Omega, cloneGeneration, unaltered clone]
-
A.
importedGeneration
Indicates that electrical energy was generated outside the local system or region and brought in for use through imports.
-
B.
currentGeneration
Indicates that an entity belongs to or is associated with the presently living or active generation within a temporal or lineage sequence.
-
C.
laterGenerationOf
Indicates that one entity belongs to a generation that comes chronologically after the generation of another entity.
-
D.
denotesGeneration
Indicates that one entity originates, produces, or gives rise to another entity, establishing a generative or causal source-result relationship between them.
-
E.
winnerGeneration
Indicates that an entity is responsible for producing, determining, or designating the winner in a given context or competition.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f664aa283c8190a869d0555eff60c6 |
completed | May 2, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f6645a615481909b53d94512ecbaf1 |
completed | May 2, 2026, 8:53 p.m. |
Created at: April 28, 2026, 11:34 a.m.