Triple
T867036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allrecipes |
E18724
|
entity |
| Predicate | allowsInteraction |
P273
|
FINISHED |
| Object | recipe comments |
—
|
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: recipe comments | Statement: [Allrecipes, allowsInteraction, recipe comments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsInteraction Context triple: [Allrecipes, allowsInteraction, recipe comments]
-
A.
allows
chosen
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
B.
hasInteraction
Indicates that there is some form of interaction or mutual action occurring between the related entities.
-
C.
allowedReturn
Indicates that an entity is permitted to be returned or sent back under specified conditions or rules.
-
D.
canPass
Indicates that one entity is able or permitted to move through, cross, or successfully traverse another entity or barrier.
-
E.
canConcurIn
Indicates that one entity is able or permitted to agree with, coincide with, or participate jointly in the same event, decision, or condition as another entity.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac7e12b0819084d25b9a66888a91 |
completed | March 1, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69a4aa87504481909618a6815948da6f |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.