Triple
T21120451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camellia House |
E520413
|
entity |
| Predicate | hasMainPlantGenus |
P111175
|
FINISHED |
| Object | Camellia |
—
|
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: Camellia | Statement: [Camellia House, hasMainPlantGenus, Camellia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainPlantGenus Context triple: [Camellia House, hasMainPlantGenus, Camellia]
-
A.
hasMajorPlant
Indicates that one entity possesses or hosts a primary or most significant plant facility or installation in relation to another entity.
-
B.
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).
-
C.
hostsPlantOf
Indicates that one entity serves as a host environment or substrate on which a particular plant lives, grows, or depends.
-
D.
hasCultivar
Indicates that one entity is a plant species or variety that possesses, includes, or is associated with a specific cultivated variety (cultivar) as another entity.
-
E.
plantGenus
chosen
Indicates that one entity is a biological genus to which the plant entity belongs.
- 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_69e0b50a623881909c0bbaf4f2c055e7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72233a43481909535560514d388be |
completed | April 21, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69e5dbff56848190a03b350a9305c612 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:55 p.m.