Triple
T35863064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macabeo |
E1037006
|
entity |
| Predicate | primaryRegionForCava |
P167030
|
FINISHED |
| Object | Penedès |
E2191305
|
NE 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: Penedès | Statement: [Macabeo, primaryRegionForCava, Penedès]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRegionForCava Context triple: [Macabeo, primaryRegionForCava, Penedès]
-
A.
coreRegionOf
Indicates that one entity constitutes the central or most essential part of another entity’s structure, area, or domain.
-
B.
primaryRegionRepresented
Indicates the main geographic or administrative region that an entity officially represents or speaks for.
-
C.
primaryHubRegion
chosen
Indicates that a given region serves as the main or central hub location for an entity or system.
-
D.
primaryRegionDepicted
Indicates that a resource primarily depicts or visually represents a particular geographic or spatial region as its main subject.
-
E.
appliesPrimarilyToSubregion
Indicates that something is mainly relevant or applicable to a specific subregion within a larger area or entity.
- F. None of above.
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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3dfabb151c8190b0ea58ab502bb5ab |
completed | June 26, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.