Triple
T1665234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haystacks series |
E35994
|
entity |
| Predicate | materialDepicted |
P30544
|
FINISHED |
| Object | harvested grain |
—
|
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: harvested grain | Statement: [Haystacks series, materialDepicted, harvested grain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: materialDepicted Context triple: [Haystacks series, materialDepicted, harvested grain]
-
A.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
B.
material
Indicates that one entity is physically composed of, made from, or constructed using the substance or material represented by the other entity.
-
C.
texture
Indicates the surface quality or feel of an entity as perceived by touch or appearance, such as being smooth, rough, soft, or coarse.
-
D.
materialInvolved
Indicates that a particular material participates in, is used by, or is otherwise involved in the referenced process, event, or relationship.
-
E.
materialProvidedFor
Indicates that one entity supplies or makes available a material for use, processing, or incorporation by another entity or purpose.
- 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_69a88606aa808190aa0b421b4271f220 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa994f92b0819084ee2f6a672334b9 |
completed | March 6, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69a907d2475c8190b7ec7dccd3335eb1 |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a94192abc0819092fc00fef9d53bcb |
completed | March 5, 2026, 8:40 a.m. |
Created at: March 4, 2026, 7:29 p.m.