Triple
T28900213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DIN 41612 |
E732931
|
entity |
| Predicate | hasMatingCycles |
P198548
|
FINISHED |
| Object | typically hundreds of mating cycles |
—
|
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: typically hundreds of mating cycles | Statement: [DIN 41612, hasMatingCycles, typically hundreds of mating cycles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMatingCycles Context triple: [DIN 41612, hasMatingCycles, typically hundreds of mating cycles]
-
A.
matingCycles
Indicates the recurring patterns or intervals at which entities engage in reproductive or mating activities.
-
B.
reproductiveMaturityAge
Indicates the age at which an organism reaches reproductive maturity and can successfully reproduce.
-
C.
hasCalvingActivity
Indicates that an entity exhibits or is associated with calving behavior or events, such as giving birth or breaking off in distinct portions.
-
D.
breedingSeasonsPerYear
Indicates how many distinct breeding periods an organism has within a single year.
-
E.
hasBreedingFocus
Indicates that an entity is the primary target or subject of another entity’s breeding efforts or breeding program.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fef2db323c8190821bda53f22a42be |
completed | May 9, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69fef21d63c88190abf6a99b59b3c655 |
completed | May 9, 2026, 8:36 a.m. |
| PDg | Predicate description generation | batch_69fef2da7d388190a5712a5094741f18 |
completed | May 9, 2026, 8:39 a.m. |
Created at: April 28, 2026, 8:02 a.m.