Triple
T21647888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mulukhiyah |
E534264
|
entity |
| Predicate | isPreparedFrom |
P95223
|
FINISHED |
| Object | fresh jute leaves |
—
|
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: fresh jute leaves | Statement: [Mulukhiyah, isPreparedFrom, fresh jute leaves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPreparedFrom Context triple: [Mulukhiyah, isPreparedFrom, fresh jute leaves]
-
A.
isPreparedAs
Indicates that one entity is made ready, arranged, or configured in a particular way or form as specified by another entity.
-
B.
preparationBy
Indicates that one entity is created, assembled, or made ready through the actions or processes performed by another entity.
-
C.
hasPreparationContext
Indicates that an entity is associated with a specific situational or environmental context in which its preparation or setup occurs.
-
D.
preparesWith
chosen
Indicates that one entity is used as a means, tool, or method by which another entity is prepared or made ready.
-
E.
preparedBefore
Indicates that one entity was prepared or made ready at an earlier time than 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_69e0c466aec88190ba39c7543dbc8ba2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef59124e1c81908d454894d66359e7 |
completed | April 27, 2026, 12:39 p.m. |
| PD | Predicate disambiguation | batch_69e696826c3c81909270791e79760937 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:35 p.m.