Triple
T16968801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Graafian follicle |
E411610
|
entity |
| Predicate | rupturesDuring |
P125435
|
FINISHED |
| Object | ovulation |
—
|
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: ovulation | Statement: [Graafian follicle, rupturesDuring, ovulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rupturesDuring Context triple: [Graafian follicle, rupturesDuring, ovulation]
-
A.
breachedDuring
Indicates that one entity violated, broke, or failed to uphold another entity (such as a rule, contract, or security measure) within a specified time period or event.
-
B.
breaksUpIn
Indicates that one entity ends or dissolves a relationship or partnership with another entity.
-
C.
disruptsContinuityOf
Indicates that one entity interrupts, breaks, or otherwise prevents the ongoing, uninterrupted progression or sequence of another entity or process.
-
D.
disruptedIn
Indicates that a normal process, function, or state is interrupted, impaired, or thrown into disorder within the specified context.
-
E.
brokenUpAt
Indicates that a romantic or close relationship between two entities ended at a specific time or date.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0a86c64819092831f8ddf1e536b |
completed | April 18, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:31 a.m.