Triple
T32946685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chiavennasca |
E842822
|
entity |
| Predicate | legalStatusInValtellina |
P198906
|
FINISHED |
| Object | principal permitted red variety |
—
|
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: principal permitted red variety | Statement: [Chiavennasca, legalStatusInValtellina, principal permitted red variety]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusInValtellina Context triple: [Chiavennasca, legalStatusInValtellina, principal permitted red variety]
-
A.
legalStatusInNepal
Indicates the legal status or standing that an entity holds under the laws and regulations of Nepal.
-
B.
statusOfSwitzerland
Indicates the political or legal condition, classification, or standing that applies to Switzerland in a given context.
-
C.
legalStatusInBelgium
Indicates the legal status or standing that an entity holds within the jurisdiction of Belgium.
-
D.
legalStatusInHomeland
Indicates the legal status or classification an entity holds within its country or place of origin.
-
E.
isInBorderCanton
Indicates that an entity is located within a canton that shares a border with another country or region.
- 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_69f3494a31f481909057136e49b4fe60 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff136ed2a881908f713401083970d1 |
completed | May 9, 2026, 10:58 a.m. |
| PD | Predicate disambiguation | batch_69ff10f9e3448190b6cb6ea5a67713c1 |
completed | May 9, 2026, 10:48 a.m. |
| PDg | Predicate description generation | batch_69ff136c68b481909b83d5b8a3693622 |
completed | May 9, 2026, 10:58 a.m. |
Created at: May 1, 2026, 1:21 a.m.