Triple
T15342595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caledonian pine forests |
E366833
|
entity |
| Predicate | characteristicPlant |
P17324
|
FINISHED |
| Object | blaeberry |
—
|
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: blaeberry | Statement: [Caledonian pine forests, characteristicPlant, blaeberry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characteristicPlant Context triple: [Caledonian pine forests, characteristicPlant, blaeberry]
-
A.
typicalLeafCharacteristic
Indicates the usual or defining features of a leaf that characterize it under normal conditions.
-
B.
flowerCharacteristic
Indicates that a flower possesses a particular attribute, quality, or feature (such as color, shape, size, or scent).
-
C.
plantType
Indicates the specific kind or category of plant that an entity is classified as.
-
D.
isPlantOf
chosen
Indicates that one entity is a plant that belongs to, is associated with, or is characteristic of another entity (such as a region, habitat, or owner).
-
E.
famousPlants
Indicates that the plants in question are widely known or celebrated, typically for their distinctive characteristics, history, or cultural significance.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e14d8088190876fceca75d12322 |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:17 a.m.