Triple
T11068063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pineau d’Aunis |
E261674
|
entity |
| Predicate | bunchCharacteristics |
P97619
|
FINISHED |
| Object | compact bunches |
—
|
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: compact bunches | Statement: [Pineau d’Aunis, bunchCharacteristics, compact bunches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bunchCharacteristics Context triple: [Pineau d’Aunis, bunchCharacteristics, compact bunches]
-
A.
catalogCharacteristic
Indicates that a catalog has a specific characteristic or attribute associated with it.
-
B.
projectCharacteristics
Indicates the defining features, qualities, or attributes that characterize a particular project.
-
C.
groupCharacterization
Indicates how a group as a whole is described or characterized in terms of its shared properties, traits, or defining features.
-
D.
codeCharacteristic
Indicates that one piece of code possesses a specific property, feature, or quality in relation to another referenced aspect.
-
E.
rulesCharacteristic
Indicates that one entity establishes or defines a characteristic, property, or feature that another entity must follow or conform to.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7992164d88190a01ed567b2529227 |
completed | April 9, 2026, 12:18 p.m. |
| PD | Predicate disambiguation | batch_69d74411d9e881908c0eeafa0f38e4b6 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:26 p.m.