Triple
T9598692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mediterranean maquis |
E231795
|
entity |
| Predicate | hasPlantTrait |
P79350
|
FINISHED |
| Object | sclerophyllous leaves |
—
|
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: sclerophyllous leaves | Statement: [Mediterranean maquis, hasPlantTrait, sclerophyllous leaves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlantTrait Context triple: [Mediterranean maquis, hasPlantTrait, sclerophyllous leaves]
-
A.
agronomicTrait
Indicates a relationship where a trait is characterized specifically in terms of its relevance to agricultural growth, management, or productivity of plants or crops.
-
B.
hasPlantPart
Indicates that one entity includes, contains, or is composed of a specific plant part of another entity.
-
C.
isPlantOf
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).
-
D.
hasPlantSymbol
Indicates that an entity is associated with or represented by a particular plant as its symbolic emblem or sign.
-
E.
hasGrowthHabit
chosen
Indicates the characteristic way in which an organism typically grows or develops in form or structure.
- 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_69ca8484838c8190b2049199d22fef70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a366d3481908db62e476958eafe |
completed | April 1, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a359788190b24f82399489f7fe |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:07 p.m.