Triple
T35455378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herb Garden |
E1024759
|
entity |
| Predicate | mayCultivate |
P183308
|
FINISHED |
| Object | woody herbs |
—
|
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: woody herbs | Statement: [Herb Garden, mayCultivate, woody herbs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayCultivate Context triple: [Herb Garden, mayCultivate, woody herbs]
-
A.
cultivationRequirement
Indicates the specific conditions or resources that must be met or provided for something to be successfully cultivated.
-
B.
isCultivated
Indicates that an entity is intentionally grown, managed, or maintained by humans rather than occurring or developing naturally without human intervention.
-
C.
methodOfCultivation
Indicates the technique or process used to grow, raise, or cultivate something (such as a crop, organism, or resource).
-
D.
cultivatedAlong
Indicates that one entity is grown or farmed in proximity to or in parallel with another entity, typically within the same area or setting.
-
E.
cultivationChallenge
Indicates a situation where the process of cultivating or growing something faces difficulty, obstacles, or increased effort.
- F. None of above. chosen
Provenance (4 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_69f76df92f108190817222e520e22268 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79da8d8848190ab5ab1bdad95d58c |
completed | May 3, 2026, 7:10 p.m. |
Created at: May 3, 2026, 4:04 p.m.