Triple
T30478361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pear |
E775504
|
entity |
| Predicate | isWidelyCultivated |
P169475
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Pear, isWidelyCultivated, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWidelyCultivated Context triple: [Pear, isWidelyCultivated, true]
-
A.
isCultivatedAs
Indicates that one entity is intentionally grown, tended, or produced by another as a crop, resource, or cultivated organism.
-
B.
isCultivated
Indicates that an entity is intentionally grown, managed, or maintained by humans rather than occurring or developing naturally without human intervention.
-
C.
cultivatedSpecies
Indicates that one entity is a species that is intentionally grown or cultivated by another entity.
-
D.
cultivatedFor
Indicates that one entity is intentionally grown, raised, or developed for the benefit, use, or purpose of another entity.
-
E.
widelyCultivatedIn
Indicates that something is grown extensively or on a large scale within a particular place or region.
- 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_69f22497341481909c21ba329fadaa6b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6871ae044819096fece430cc1f9f9 |
completed | May 2, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 8:12 p.m.