Triple
T37371961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halutza |
E927866
|
entity |
| Predicate | primaryTradeCommodity |
P61379
|
FINISHED |
| Object | frankincense |
—
|
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: frankincense | Statement: [Halutza, primaryTradeCommodity, frankincense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTradeCommodity Context triple: [Halutza, primaryTradeCommodity, frankincense]
-
A.
allegedPrimaryCommodity
Indicates that something is claimed or reported, but not confirmed, to be the main commodity associated with an entity or activity.
-
B.
commodityProduced
Indicates that a particular commodity is generated, manufactured, or otherwise produced by a specified entity or process.
-
C.
majorTradeType
Indicates the primary category or kind of trade activity that characterizes the relationship between the involved entities.
-
D.
primaryTrade
chosen
Indicates that the referenced activity or exchange is the main or most significant trade relationship associated with the entities involved.
-
E.
commodityType
Indicates the classification of a good or product according to its type or category within a commodity system.
- 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_69f76eb820248190a5c395ca50ad002a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.