Triple
T13972575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elbling |
E336100
|
entity |
| Predicate | ageability |
P106670
|
FINISHED |
| Object | bestConsumedYoung |
—
|
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: bestConsumedYoung | Statement: [Elbling, ageability, bestConsumedYoung]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageability Context triple: [Elbling, ageability, bestConsumedYoung]
-
A.
ageStatus
Indicates the relationship between an entity and its classification into an age-related category or status (e.g., minor, adult, senior).
-
B.
mayBeAgedIn
chosen
Indicates that an entity has the potential or option to undergo an aging or maturation process in a specified medium, container, or environment.
-
C.
ageBased
Indicates a relationship or condition that depends on or is determined by the age of the entities involved.
-
D.
ageProgression
Indicates a temporal relationship where an entity’s age increases or advances over time.
-
E.
typicalAgingTime
Indicates the usual duration required for something to age or mature under normal conditions.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e8eae40819080dd4bd25c73b6d6 |
completed | April 14, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69dd465a21408190b912a42c50ffa0d9 |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:18 p.m.