Triple
T21812772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Bovine Meat Agreement |
E538517
|
entity |
| Predicate | hasCommodityScope |
P16090
|
FINISHED |
| Object | bovine animals |
—
|
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: bovine animals | Statement: [International Bovine Meat Agreement, hasCommodityScope, bovine animals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommodityScope Context triple: [International Bovine Meat Agreement, hasCommodityScope, bovine animals]
-
A.
hasMarketCommodity
Indicates that an entity is associated with or trades in a particular commodity within a market context.
-
B.
scopeOfSales
Indicates the range, extent, or boundaries within which sales activities, rights, or transactions are valid or permitted.
-
C.
scopeOfProducts
chosen
Indicates the range or extent of products that fall under a particular category, responsibility, or context.
-
D.
hasRegulationScope
Indicates that a regulation applies to, or governs, a specified scope, domain, or area of relevance.
-
E.
acquisitionScope
Indicates the extent, boundaries, or coverage of what is obtained or brought under control through an acquisition.
- 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07cc7ec1c8190a5420b44a49ae32f |
completed | April 28, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69e6be815a108190be81d7c987d0c0d6 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:53 p.m.