Triple
T7236075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irwin mango |
E155229
|
entity |
| Predicate | marketTrait |
P75940
|
FINISHED |
| Object | attractive appearance |
—
|
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: attractive appearance | Statement: [Irwin mango, marketTrait, attractive appearance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketTrait Context triple: [Irwin mango, marketTrait, attractive appearance]
-
A.
market
Indicates the act of promoting, advertising, or selling a product, service, or idea to potential buyers or target audiences.
-
B.
marketModel
Indicates the specific economic or pricing framework under which transactions or interactions in a market are structured and governed.
-
C.
marketType
Indicates the classification or category of market in which an entity operates or a transaction occurs (e.g., retail, wholesale, online).
-
D.
coreMarket
Indicates that an entity serves as the primary or most important market for another entity’s products, services, or activities.
-
E.
marketContext
Indicates the broader economic, competitive, and situational conditions under which a product, service, or transaction is positioned or evaluated.
- 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_69c688143bfc81908d4176617735e601 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea552a688190a00f5d0ad982f787 |
completed | March 27, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69c6e7644648819096a5e2de5d0dbe97 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6ea539f5c81908001524149903559 |
completed | March 27, 2026, 8:36 p.m. |
Created at: March 27, 2026, 2:55 p.m.