Triple
T22692426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gems (Gemini of Cajal bodies) |
E561084
|
entity |
| Predicate | dynamicDuring |
P144151
|
FINISHED |
| Object | cell cycle |
—
|
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: cell cycle | Statement: [gems (Gemini of Cajal bodies), dynamicDuring, cell cycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynamicDuring Context triple: [gems (Gemini of Cajal bodies), dynamicDuring, cell cycle]
-
A.
modifiedDuring
Indicates that one entity underwent a change or alteration while another specified time period, process, or event was occurring.
-
B.
dynamicProcess
chosen
Indicates an ongoing, evolving sequence of changes or interactions that unfold over time rather than a fixed or static state.
-
C.
constructedDuring
Indicates that one entity was built or created within the time period defined by another entity or event.
-
D.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
E.
dynamicCharacter
Indicates that a character undergoes significant internal change or development over the course of a narrative.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789ba0148190891781d05ec64f3c |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:13 p.m.