Triple
T8467089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mus musculus |
E200190
|
entity |
| Predicate | sexualMaturity |
P16092
|
FINISHED |
| Object | about 6–8 weeks |
—
|
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: about 6–8 weeks | Statement: [Mus musculus, sexualMaturity, about 6–8 weeks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sexualMaturity Context triple: [Mus musculus, sexualMaturity, about 6–8 weeks]
-
A.
maturity
chosen
Indicates that an entity has reached a specified stage of development, completeness, or readiness, often marking the point at which certain rights, obligations, or behaviors become applicable.
-
B.
sexStatusAtStud
Indicates the reproductive or sexual condition of an animal at the time it is used for breeding or stud purposes.
-
C.
hasSex
Indicates that one entity engages in sexual activity with another entity.
-
D.
reproductiveType
Indicates the mode or strategy by which an organism reproduces or generates offspring.
-
E.
maturityType
Indicates the kind or category of maturity associated with an entity, such as how or when an obligation, product, or process reaches its full or due state.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4d2eb648190b606411eb6a8f7ea |
completed | March 31, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.