Triple
T2542437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crataegus |
E57813
|
entity |
| Predicate | hasHybridization |
P39441
|
FINISHED |
| Object | frequent natural hybrids within genus |
—
|
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: frequent natural hybrids within genus | Statement: [Crataegus, hasHybridization, frequent natural hybrids within genus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHybridization Context triple: [Crataegus, hasHybridization, frequent natural hybrids within genus]
-
A.
hasComb
Indicates that an entity possesses or is equipped with a comb.
-
B.
hasPhylum
Indicates that an entity (typically a biological taxon or organism) is classified as belonging to a particular phylum in a taxonomic hierarchy.
-
C.
hasHyphenatedIdentity
Indicates that an entity possesses a compound or dual identity expressed as a hyphenated combination of distinct identity components.
-
D.
hasXylem
Indicates that an entity possesses xylem tissue or structures for conducting water and nutrients.
-
E.
hasComplex
Indicates that one entity possesses, is associated with, or is part of a larger composite structure or complex formed with another entity.
- 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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2bd92f88190bf100c799f62210c |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0c63964819092d5f578195ae8dd |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1c7b6e48190be9a0c31069df797 |
completed | March 7, 2026, 7:20 a.m. |
Created at: March 6, 2026, 9:47 p.m.