Triple
T19750972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juniperus osteosperma |
E474369
|
entity |
| Predicate | seedDispersedBy |
P43554
|
FINISHED |
| Object | birds |
—
|
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: birds | Statement: [Juniperus osteosperma, seedDispersedBy, birds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seedDispersedBy Context triple: [Juniperus osteosperma, seedDispersedBy, birds]
-
A.
seedDispersal
Indicates the process by which seeds are transported away from the parent organism to new locations, often via wind, water, or animals.
-
B.
dispersalAbility
Indicates the capacity or effectiveness with which an entity can spread or be dispersed from one location to others.
-
C.
dispersalVector
chosen
Indicates the means or agent by which something (such as an organism, propagule, or substance) is spread or transported from one location to another.
-
D.
seedEnclosure
Indicates that one entity serves as a container or protective space in which another entity’s seeds are held or stored.
-
E.
dispersalUnit
Indicates the type or form of unit in which something (such as seeds, spores, or organisms) is spread or dispersed from one place to another.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65299a7048190a9b22307ac06bd03 |
completed | April 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.