Triple
T23383834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beyond Sausage |
E593822
|
entity |
| Predicate | intendedToReplicate |
P18373
|
FINISHED |
| Object | pork sausage |
—
|
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: pork sausage | Statement: [Beyond Sausage, intendedToReplicate, pork sausage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedToReplicate Context triple: [Beyond Sausage, intendedToReplicate, pork sausage]
-
A.
replicaOf
chosen
Indicates that one entity is an exact or near-exact copy of another entity, preserving its form, structure, or content.
-
B.
intendedToMerge
Indicates that one entity had the purpose or plan to combine or consolidate with another entity into a single unit.
-
C.
intendsTo
Indicates that one entity has the purpose, plan, or desire to perform an action involving another entity or outcome.
-
D.
intendedWith
Indicates that one entity is the planned or desired target, recipient, or context for the use or application of another entity.
-
E.
replicatesDuring
Indicates that one entity undergoes replication during the time period, phase, or process specified by the other 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a496ae34819090e86c89eef6d2dc |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:34 p.m.