Triple
T6934290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luria–Delbrück experiment |
E160513
|
entity |
| Predicate | dataCharacteristic |
P74365
|
FINISHED |
| Object | jackpot events of early mutations |
—
|
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: jackpot events of early mutations | Statement: [Luria–Delbrück experiment, dataCharacteristic, jackpot events of early mutations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataCharacteristic Context triple: [Luria–Delbrück experiment, dataCharacteristic, jackpot events of early mutations]
-
A.
catalogCharacteristic
Indicates that a catalog has a specific characteristic or attribute associated with it.
-
B.
equipmentCharacteristic
Indicates that a specific characteristic, property, or attribute is associated with a piece of equipment.
-
C.
podCharacteristic
Indicates a characteristic, feature, or property that is attributed to a pod.
-
D.
describesCharacteristicOf
Indicates that one entity expresses or specifies a characteristic, feature, or property of another entity.
-
E.
transportCharacteristic
Indicates a relationship where a specific characteristic, property, or feature is attributed to a mode or instance of transport.
- 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_69c6884e15208190b9e91487eaafcf85 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e0c74fe48190aeaa018631e52ef6 |
completed | March 27, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bd5a388190a57a96d925696ff6 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6e0c620f0819080e0ec49b36d4c30 |
completed | March 27, 2026, 7:55 p.m. |
Created at: March 27, 2026, 2:27 p.m.