Triple
T33704224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Filet mignon |
E863540
|
entity |
| Predicate | cutFrom |
P177221
|
FINISHED |
| Object | tenderloin |
—
|
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: tenderloin | Statement: [Filet mignon, cutFrom, tenderloin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cutFrom Context triple: [Filet mignon, cutFrom, tenderloin]
-
A.
cutInto
Indicates that one entity divides another entity into smaller pieces or segments.
-
B.
cutBy
Indicates that one entity is divided, severed, or shaped as a result of another entity performing a cutting action on it.
-
C.
cutaway
Indicates that one entity removes or separates a part or section from another entity, typically by cutting.
-
D.
cutFormat
Indicates that one entity trims or shapes another entity into a specified format or pattern.
-
E.
cutOff
Indicates that one entity causes another entity to be disconnected, interrupted, or severed from a source, flow, or continuation.
- F. None of above. chosen
Provenance (4 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_69f3498844608190bb8f9b14908d2510 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fae2a7a8819099945d1706a94bfd |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fa335b908190a20d92d5396203b5 |
completed | May 3, 2026, 7:33 a.m. |
Created at: May 1, 2026, 1:43 a.m.