Triple
T20159288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Vine |
E491660
|
entity |
| Predicate | annualYield |
P138889
|
FINISHED |
| Object | approximately 25 kilograms of grapes |
—
|
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: approximately 25 kilograms of grapes | Statement: [Old Vine, annualYield, approximately 25 kilograms of grapes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: annualYield Context triple: [Old Vine, annualYield, approximately 25 kilograms of grapes]
-
A.
annualFrom
Indicates that something recurs or is calculated on a yearly basis starting from a specified point in time.
-
B.
annualReturnDate
Indicates the date each year on which a recurring return, report, or filing is due or takes effect.
-
C.
isAnnual
Indicates that something occurs, is scheduled, or is valid once every year.
-
D.
commissionYear
Indicates the year in which something (such as a work, project, or asset) was formally commissioned or authorized to be created or undertaken.
-
E.
appliesInYears
Indicates that something (such as a rule, condition, or effect) is valid, relevant, or in force during specific years.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e667e27aa88190a326288b992ea274 |
completed | April 20, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69e54cfd924881909b55f3e4d3e7e070 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc2bc3c819088c33cd263303433 |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 11:34 p.m.