Triple
T29400021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casablanca Valley |
E745608
|
entity |
| Predicate | hasSubRegionType |
P97770
|
FINISHED |
| Object | coastal-influenced vineyards |
—
|
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: coastal-influenced vineyards | Statement: [Casablanca Valley, hasSubRegionType, coastal-influenced vineyards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubRegionType Context triple: [Casablanca Valley, hasSubRegionType, coastal-influenced vineyards]
-
A.
hasSubregionRelationWith
Indicates a relationship where one region is a subregion or contained part of another region.
-
B.
hasSubregionStatus
Indicates that one region holds an official or defined status as a subregion within a larger geographic or administrative area.
-
C.
hasSubregionStyle
Indicates a stylistic relationship in which one region exhibits a specific style that is characteristic of a subregion within it.
-
D.
isInSubregion
Indicates that one region or area is located within the boundaries of another, more specific subregion.
-
E.
containsRegionType
chosen
Indicates that one region includes or encompasses another region of a specified type within its spatial or logical boundaries.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: April 28, 2026, 2:49 p.m.