Triple
T22357087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calvin cycle |
E552680
|
entity |
| Predicate | canOccurWithout |
P64000
|
FINISHED |
| Object | direct light |
—
|
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: direct light | Statement: [Calvin cycle, canOccurWithout, direct light]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canOccurWithout Context triple: [Calvin cycle, canOccurWithout, direct light]
-
A.
canBeUsedWithout
chosen
Indicates that one entity is capable of functioning or being utilized independently of another specified entity.
-
B.
cannotBeUsedWithout
Indicates that one entity is dependent on another such that it cannot function, operate, or be utilized unless the other entity is also present or in use.
-
C.
succeedsInAbsenceOf
Indicates that one entity successfully achieves or maintains something only when another specified entity or condition is not present.
-
D.
occursWhen
Indicates that one event or condition happens at the same time or is triggered under the circumstances defined by another event or condition.
-
E.
occursFor
Indicates that an event, process, or condition takes place in relation to, or on behalf of, a particular entity or context.
- 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_69e11e4a0ad08190a385b4d343cf6524 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157d08b148190a9a4e445e8579219 |
completed | April 29, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:44 p.m.