Triple
T26934844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pecan Capital of the World |
E678343
|
entity |
| Predicate | productTypeHighlighted |
P36108
|
FINISHED |
| Object | pecans |
—
|
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: pecans | Statement: [Pecan Capital of the World, productTypeHighlighted, pecans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productTypeHighlighted Context triple: [Pecan Capital of the World, productTypeHighlighted, pecans]
-
A.
productTypePromoted
chosen
Indicates that a particular type or category of product is being actively promoted or highlighted, such as through marketing, placement, or special offers.
-
B.
typeOfProducts
Indicates the kinds or categories of products that are associated with or offered by an entity.
-
C.
eligibleProducts
Indicates that certain products meet the required criteria or conditions to qualify for a specified offer, action, or status.
-
D.
productFor
Indicates that one entity is intended to be used by, with, or in relation to another entity as its product or offering.
-
E.
portraysProduct
Indicates that one entity visually or narratively represents, depicts, or features 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_69eeeb4cac908190a45956c2993d1cc2 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 27, 2026, 6:15 a.m.