Triple
T18668689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Mancha wines |
E456408
|
entity |
| Predicate | countryRegulation |
P34675
|
FINISHED |
| Object | Spanish wine law |
—
|
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: Spanish wine law | Statement: [La Mancha wines, countryRegulation, Spanish wine law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryRegulation Context triple: [La Mancha wines, countryRegulation, Spanish wine law]
-
A.
countryLegalFramework
Indicates the legal system, regulations, and institutional rules that govern actions and relationships within a given country.
-
B.
countryJurisdiction
Indicates that one country has legal authority, control, or governing power over a specified territory, entity, or matter.
-
C.
regulatorCountry
Indicates the country that has regulatory authority or oversight over the referenced entity or activity.
-
D.
hasRegulations
chosen
Indicates that one entity imposes, contains, or is associated with rules or regulatory requirements that govern the behavior or operation of another entity.
-
E.
displayRegulation
Indicates that an entity presents or shows a regulation or set of rules, making it visible or accessible to others.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e556b0502881909ea05f2746163746 |
completed | April 19, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.