Triple
T35830047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paso Robles Westside |
E1035770
|
entity |
| Predicate | isRenownedPortionOf |
P136851
|
FINISHED |
| Object | Paso Robles wine country |
—
|
NE NERFINISHED |
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: Paso Robles wine country | Statement: [Paso Robles Westside, isRenownedPortionOf, Paso Robles wine country]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRenownedPortionOf Context triple: [Paso Robles Westside, isRenownedPortionOf, Paso Robles wine country]
-
A.
isWidelyKnown
Indicates that something is generally recognized or familiar to a large number of people.
-
B.
isWidelyKnownAs
Indicates that an entity is commonly referred to or recognized by a particular name or label by a broad audience.
-
C.
reconocidaPor
Indicates that an entity is recognized, acknowledged, or honored by another entity.
-
D.
isOneOfMostProminentIn
chosen
Indicates that an entity ranks among the most notable, influential, or widely recognized members within a specified group, category, or domain.
-
E.
isKnownPrimarilyByName
Indicates that an entity is chiefly recognized or identified by its name rather than by other attributes or characteristics.
- 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_69f76e192a94819082db360cb91e6a8d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.