Triple
T25585956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mungyeong |
E641381
|
entity |
| Predicate | hasSpecialLocalProduct |
P3585
|
FINISHED |
| Object | omija (schisandra) berries |
—
|
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: omija (schisandra) berries | Statement: [Mungyeong, hasSpecialLocalProduct, omija (schisandra) berries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecialLocalProduct Context triple: [Mungyeong, hasSpecialLocalProduct, omija (schisandra) berries]
-
A.
hasSpecial
Indicates that an entity possesses or is associated with a distinctive or exceptional attribute, status, or feature compared to others.
-
B.
shopSpecialty
Indicates that a shop primarily focuses on or is specially known for offering a particular type of product or service.
-
C.
hasSpecials
Indicates that an entity offers or is associated with special deals, promotions, or limited-time offers.
-
D.
hasLocalMarketFunction
Indicates that an entity serves a local market role or function, such as providing goods, services, or economic activities primarily to a nearby or community-based customer base.
-
E.
hasProduct
chosen
Indicates that an entity possesses, offers, or is associated with a particular product.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 21, 2026, 4:16 p.m.