Triple
T29669989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Encruzado |
E750640
|
entity |
| Predicate | typicalBlendPartnerRegion |
P203800
|
FINISHED |
| Object | other Dão white varieties |
—
|
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: other Dão white varieties | Statement: [Encruzado, typicalBlendPartnerRegion, other Dão white varieties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBlendPartnerRegion Context triple: [Encruzado, typicalBlendPartnerRegion, other Dão white varieties]
-
A.
participantsRegion
Indicates that the related entities are associated with, originate from, or operate within a specified geographic region.
-
B.
typicalHostRegion
Indicates the geographic region where a host is most commonly or characteristically found or associated.
-
C.
homeGroundRegion
Indicates that a sports team’s primary home venue is located within a specified geographic region.
-
D.
ITURegion
Indicates the International Telecommunication Union (ITU) regional classification to which an entity (such as a location or station) belongs.
-
E.
regionOfHostCountry
Indicates that one entity is a geographic or administrative region belonging to, or located within, the specified host country.
- 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a0207a1272c81909dcdb6e3307702f5 |
completed | May 11, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_6a0205fa1e608190829fd2baa0434fff |
completed | May 11, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_6a0207a073508190adf36e94ab2380ad |
completed | May 11, 2026, 4:45 p.m. |
Created at: April 28, 2026, 7:04 p.m.