Triple
T14227764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peberholm |
E352666
|
entity |
| Predicate | floraOrigin |
P83264
|
FINISHED |
| Object | natural colonisation |
—
|
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: natural colonisation | Statement: [Peberholm, floraOrigin, natural colonisation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floraOrigin Context triple: [Peberholm, floraOrigin, natural colonisation]
-
A.
cultivarOrigin
Indicates that a particular plant cultivar was originally developed, bred, or derived from a specified source location, population, or lineage.
-
B.
associatedFlora
chosen
Indicates a relationship where specific plants or vegetation are characteristically linked to, occur with, or are commonly found in association with a given entity or environment.
-
C.
hasFloralRegion
Indicates that one entity possesses or is associated with a specific floral region as a characteristic or component.
-
D.
soilOrigin
Indicates the source or provenance from which a given soil was formed or obtained.
-
E.
hasRegionalFlower
Indicates that a region is associated with a specific flower designated as its symbolic or representative flower.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de622a48508190bbfedb762bd1674d |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:07 a.m.