Triple
T20603180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colletia hystrix |
E506233
|
entity |
| Predicate | hasBranchingPattern |
P10586
|
FINISHED |
| Object | broom-like branches |
—
|
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: broom-like branches | Statement: [Colletia hystrix, hasBranchingPattern, broom-like branches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBranchingPattern Context triple: [Colletia hystrix, hasBranchingPattern, broom-like branches]
-
A.
branchingPattern
chosen
Indicates the structural way in which one element divides into multiple offshoots or subdivisions from a common source.
-
B.
hasBranches
Indicates that an entity extends into multiple subordinate parts or offshoots, like limbs, divisions, or sections stemming from a main source.
-
C.
hasBranchLinePurpose
Indicates that a branch line is associated with a specific intended function or purpose within a larger network or system.
-
D.
hasTwoBranches
Indicates that the related entity is divided into or composed of exactly two distinct branches.
-
E.
possibleBranch
Indicates that one entity can serve as an alternative or potential continuation path branching from another entity.
- 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aa22663881909a8d4644e1c48dc2 |
completed | April 20, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:41 a.m.