Triple
T27329860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trat Province |
E689764
|
entity |
| Predicate | hasMainAgriculturalProduct |
P1897
|
FINISHED |
| Object | rubber |
—
|
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: rubber | Statement: [Trat Province, hasMainAgriculturalProduct, rubber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainAgriculturalProduct Context triple: [Trat Province, hasMainAgriculturalProduct, rubber]
-
A.
hasAgriculturalProduction
Indicates that an entity engages in or is characterized by the production of agricultural goods such as crops or livestock.
-
B.
hasAgriculturalType
Indicates that an entity is associated with or classified by a specific type or category of agriculture.
-
C.
agriculturalProduce
Indicates that one entity is an agricultural product (such as crops or livestock-derived goods) produced by or associated with another entity.
-
D.
majorCrop
chosen
Indicates that a particular crop is one of the primary or most important crops cultivated in a given area or context.
-
E.
isCultivatedAs
Indicates that one entity is intentionally grown, tended, or produced by another as a crop, resource, or cultivated organism.
- 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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: April 27, 2026, 11:37 a.m.