Triple
T2261631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muscadelle |
E50051
|
entity |
| Predicate | sensitivity |
P24994
|
FINISHED |
| Object | susceptible to rot |
—
|
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: susceptible to rot | Statement: [Muscadelle, sensitivity, susceptible to rot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sensitivity Context triple: [Muscadelle, sensitivity, susceptible to rot]
-
A.
sensitivityFeature
chosen
Indicates a relationship where one entity functions as a sensitivity-related characteristic, parameter, or attribute of another entity.
-
B.
sentience
Indicates that an entity possesses the capacity for subjective experience, awareness, or feeling.
-
C.
sensitivityRegion
Indicates the specific area or domain within which a subject is particularly responsive, vulnerable, or reactive to a given influence or condition.
-
D.
primarySense
Indicates that one sense or meaning of an entity is designated as its main or most central sense among possible alternatives.
-
E.
feels
Indicates that an entity experiences or has a particular emotion, sensation, or internal state in relation to something.
- 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_69a88b01e0048190ba96431b5f990ba9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc2ea65288190bc8644a07a11dfa9 |
completed | March 7, 2026, 6:17 a.m. |
| PD | Predicate disambiguation | batch_69abbdb592588190ac1ef5e8c54575b1 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.