Triple
T28579364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oaxacan cheese |
E723328
|
entity |
| Predicate | usedAsSubstituteFor |
P6280
|
FINISHED |
| Object | mozzarella in Mexican dishes |
—
|
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: mozzarella in Mexican dishes | Statement: [Oaxacan cheese, usedAsSubstituteFor, mozzarella in Mexican dishes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsSubstituteFor Context triple: [Oaxacan cheese, usedAsSubstituteFor, mozzarella in Mexican dishes]
-
A.
alternativeUsedBy
Indicates that one entity serves as an alternative option or substitute that is used in place of another entity.
-
B.
usedInsteadOf
chosen
Indicates that one entity is employed or chosen as a substitute or replacement for another entity.
-
C.
developedAsReplacementFor
Indicates that one entity was created or designed specifically to take the place of another entity, serving as its successor or substitute.
-
D.
involvesSubstitute
Indicates that one entity participates in a situation, event, or role as a replacement or stand-in for another entity.
-
E.
numberOfSubstitutes
Indicates the quantity of substitute entities associated with or allowed for a given entity or situation.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 28, 2026, 4:14 a.m.