Triple
T962509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juniperus communis |
E20765
|
entity |
| Predicate | coneMaturationTime |
P2080
|
FINISHED |
| Object | about 18 months |
—
|
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 18 months | Statement: [Juniperus communis, coneMaturationTime, about 18 months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coneMaturationTime Context triple: [Juniperus communis, coneMaturationTime, about 18 months]
-
A.
ripeningTime
chosen
Indicates the period or duration required for something to become fully ripe or reach its mature, ready-to-use state.
-
B.
maturityRange
Indicates the span or limits of maturity (such as age, development stage, or readiness) within which the related entities or conditions are considered applicable.
-
C.
timeToComplete
Indicates the duration required for an entity or process to be fully completed.
-
D.
maturity
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.
-
E.
coneType
Indicates the specific category or style of cone associated with an entity (e.g., type, shape, or design of the cone).
- 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_69a493b21f2881908132dcf45dcd2f36 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b415ac688190bbcef455935a3116 |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a2e23c8190b932fe88b02f995d |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.