Triple
T10896958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gouet |
E257333
|
entity |
| Predicate | typicalYield |
P32569
|
FINISHED |
| Object | high-yielding vine |
—
|
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: high-yielding vine | Statement: [Gouet, typicalYield, high-yielding vine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalYield Context triple: [Gouet, typicalYield, high-yielding vine]
-
A.
yieldPotential
chosen
Indicates the expected amount or capacity of output, production, or benefit that something can generate under given conditions.
-
B.
typicalProductionType
Indicates the usual or characteristic type of production activity associated with an entity.
-
C.
yieldClassification
Indicates how an outcome, result, or production level is categorized or labeled according to predefined yield criteria.
-
D.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
E.
typicalSeed
Indicates that something is a usual or characteristic seed for a given plant or context.
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75d02e4c88190b8286078e90bf913 |
completed | April 9, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.