Triple
T1818382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IR64 |
E40486
|
entity |
| Predicate | hasMarketPreference |
P25915
|
FINISHED |
| Object | consumer-acceptable grain quality |
—
|
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: consumer-acceptable grain quality | Statement: [IR64, hasMarketPreference, consumer-acceptable grain quality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarketPreference Context triple: [IR64, hasMarketPreference, consumer-acceptable grain quality]
-
A.
marketPreference
chosen
Indicates a relationship where one entity favors, targets, or prioritizes a particular market or market segment over others.
-
B.
hasMarket
Indicates that an entity possesses, operates in, or is associated with a particular market or marketplace.
-
C.
hasMarketingCategory
Indicates that an entity is associated with a specific marketing category or segment used for classification or targeting.
-
D.
hasMajorMarket
Indicates that an entity has a primary or most significant market in a specified location or segment.
-
E.
hasMarketData
Indicates that an entity possesses or is associated with relevant market-related information or statistics.
- 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_69a8864526c081908a3a4d74f689e2c5 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aba67721788190951beae25e885457 |
completed | March 7, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69aa61d884548190a19cf3a6b5ae9d48 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:32 p.m.