Triple
T12075735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prosciutto di Parma |
E287541
|
entity |
| Predicate | commonPairing |
P69696
|
FINISHED |
| Object | melon |
—
|
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: melon | Statement: [Prosciutto di Parma, commonPairing, melon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonPairing Context triple: [Prosciutto di Parma, commonPairing, melon]
-
A.
commonPair
chosen
Indicates that two entities commonly occur together or are frequently associated as a pair in some shared context.
-
B.
starPairing
Indicates a relationship where two stars are associated or grouped together as a pair, typically for observational, analytical, or classificatory purposes.
-
C.
dualPair
Indicates that two entities form a dual pair, standing in a mathematically defined dual relationship where each is the dual counterpart of the other.
-
D.
pairBond
Indicates a long-term, typically exclusive social or reproductive partnership formed between two individuals.
-
E.
canPairRegistersFor
Indicates that two registers are compatible and allowed to be paired together for a combined or coordinated operation.
- 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_69d6ab4846e081908ee7bbd66a6d3459 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bf4f508190842927e7e0642235 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:48 p.m.