Triple
T37665125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purpur Block |
E937803
|
entity |
| Predicate | craftingInput |
P192112
|
FINISHED |
| Object | Popped Chorus Fruit |
—
|
NE NERFINISHED |
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: Popped Chorus Fruit | Statement: [Purpur Block, craftingInput, Popped Chorus Fruit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: craftingInput Context triple: [Purpur Block, craftingInput, Popped Chorus Fruit]
-
A.
craftingWith
Indicates a relationship where something is created or shaped using a particular tool, material, or method.
-
B.
craftingGrid
Indicates a relationship where items are arranged in a specific grid layout to be combined or crafted into a new item or outcome.
-
C.
craftable
Indicates that one entity can be created, assembled, or produced from other entities or resources, typically through a defined crafting process.
-
D.
craftedIn
Indicates that an object or work was created or produced at a particular place or within a specific location.
-
E.
exampleCraft
Indicates that an entity creates, designs, or skillfully produces another entity, typically as a crafted example or artifact.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69fcf36bb86c8190a0a0ccf47cb56e5c |
completed | May 7, 2026, 8:17 p.m. |
Created at: May 3, 2026, 4:18 p.m.