Triple
T2261628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muscadelle |
E50051
|
entity |
| Predicate | notRelatedTo |
P8167
|
FINISHED |
| Object | Muscat family of grapes |
—
|
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: Muscat family of grapes | Statement: [Muscadelle, notRelatedTo, Muscat family of grapes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notRelatedTo Context triple: [Muscadelle, notRelatedTo, Muscat family of grapes]
-
A.
notGeneticallyRelatedTo
chosen
Indicates that there is no genetic or hereditary relationship between the two entities.
-
B.
doesNot
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
C.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
-
D.
moreDistantlyRelatedTo
Indicates that one entity is related to another by a more distant or indirect relationship compared to some closer reference relationship.
-
E.
notObservedIn
Indicates that a particular entity, event, or property has not been detected, recorded, or seen within a specified context, dataset, or environment.
- 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.