Triple
T22752231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pedro Ximénez |
E562732
|
entity |
| Predicate | typicalAgingVessel |
P26083
|
FINISHED |
| Object | oak cask |
—
|
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: oak cask | Statement: [Pedro Ximénez, typicalAgingVessel, oak cask]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAgingVessel Context triple: [Pedro Ximénez, typicalAgingVessel, oak cask]
-
A.
typicalAgingIndication
Indicates that something serves as a sign or marker commonly associated with the normal process of aging.
-
B.
affectedVessel
Indicates that a vessel is impacted, influenced, or acted upon by a specified event, condition, or process.
-
C.
typicalAgingTime
Indicates the usual duration required for something to age or mature under normal conditions.
-
D.
primaryVessels
Indicates that the related vessels are the main or principal ones within a given system, structure, or context.
-
E.
hasVessel
chosen
Indicates that one entity possesses, uses, or is associated with a particular vessel (such as a container, ship, or transport medium) in the context of the described relationship or action.
- 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179baa85881909140f41f2428cc98 |
completed | April 29, 2026, 3:23 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:24 p.m.