Triple
T6997876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Protected Geographical Indication |
E162262
|
entity |
| Predicate | exampleProduct |
P3585
|
FINISHED |
| Object | Scotch Beef PGI |
—
|
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: Scotch Beef PGI | Statement: [Protected Geographical Indication, exampleProduct, Scotch Beef PGI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exampleProduct Context triple: [Protected Geographical Indication, exampleProduct, Scotch Beef PGI]
-
A.
productForm
Indicates the specific physical or presentation format in which a product is offered or delivered (e.g., tablet, liquid, package type).
-
B.
exportProduct
Indicates that an entity sends or sells a product from its own country or region to another country or external market.
-
C.
hasProduct
chosen
Indicates that an entity possesses, offers, or is associated with a particular product.
-
D.
productDomain
Indicates the domain, field, or area of application to which a given product belongs or is relevant.
-
E.
commercialProduct
Indicates that one entity is a product or service offered for sale or commercial use by another entity.
- 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_69c68857ffc08190857dc62cd5253777 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbeef57881909245c8a5374a8111 |
completed | March 27, 2026, 7:35 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c67c94819084fdcf0398606027 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:33 p.m.