Triple
T16968798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Graafian follicle |
E411610
|
entity |
| Predicate | hormoneSecretion |
P125367
|
FINISHED |
| Object | estradiol |
—
|
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: estradiol | Statement: [Graafian follicle, hormoneSecretion, estradiol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hormoneSecretion Context triple: [Graafian follicle, hormoneSecretion, estradiol]
-
A.
hormonesConcerned
Indicates that a particular process, condition, or interaction involves or is regulated by specific hormones.
-
B.
secretedInResponseTo
Indicates that a substance is released or discharged as a direct reaction to a specific stimulus, condition, or event.
-
C.
skinSecretionFunction
Indicates the function or role served by a substance secreted through the skin in the context of an organism’s biology or behavior.
-
D.
containsHormoneType
chosen
Indicates that one entity includes or is associated with a specific type or category of hormone.
-
E.
reproductiveSystem
Indicates a relationship where one entity is the reproductive system of another, responsible for producing offspring or reproductive cells.
- 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_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. |
Created at: April 10, 2026, 5:31 a.m.