Triple
T7119065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Garden |
E165900
|
entity |
| Predicate | plantCollectionFocus |
P36488
|
FINISHED |
| Object | plants characteristic of California |
—
|
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: plants characteristic of California | Statement: [California Garden, plantCollectionFocus, plants characteristic of California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plantCollectionFocus Context triple: [California Garden, plantCollectionFocus, plants characteristic of California]
-
A.
plantCollection
chosen
Indicates that one entity maintains or possesses a collection of plants, typically grouped or curated as a set.
-
B.
plantType
Indicates the specific kind or category of plant that an entity is classified as.
-
C.
famousPlants
Indicates that the plants in question are widely known or celebrated, typically for their distinctive characteristics, history, or cultural significance.
-
D.
involvesPlant
Indicates that the relationship or action includes or pertains to a plant as a participating entity.
-
E.
isHouseplant
Indicates that an entity is a plant typically grown and kept indoors as a houseplant.
- 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_69c6888227bc8190a1394679e3116f90 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e61b8a288190a165ea25adfaaef5 |
completed | March 27, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c4f9788190830288d00cc37026 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:43 p.m.