Triple
T19904799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abies |
E478384
|
entity |
| Predicate | coneDisintegration |
P137767
|
FINISHED |
| Object | cones disintegrate on the tree |
—
|
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: cones disintegrate on the tree | Statement: [Abies, coneDisintegration, cones disintegrate on the tree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coneDisintegration Context triple: [Abies, coneDisintegration, cones disintegrate on the tree]
-
A.
decayProduct
Indicates that one entity is the resulting product formed when another entity undergoes a decay process.
-
B.
decayWidth
Indicates the total probability per unit time (or corresponding energy measure) that an unstable particle will decay via all possible channels.
-
C.
coneType
Indicates the specific category or style of cone associated with an entity (e.g., type, shape, or design of the cone).
-
D.
decayMode
Indicates the specific process or pathway by which an unstable entity transforms or decays into other products.
-
E.
decayEnergy
Indicates the amount of energy released or carried away when an unstable entity undergoes a decay process.
- 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65945cc2081908224902d5f042d7a |
completed | April 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:52 p.m.