Triple
T27986047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cartojal wine |
E706744
|
entity |
| Predicate | mainConsumerBase |
P77700
|
FINISHED |
| Object | visitors to the Málaga Fair |
—
|
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: visitors to the Málaga Fair | Statement: [Cartojal wine, mainConsumerBase, visitors to the Málaga Fair]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainConsumerBase Context triple: [Cartojal wine, mainConsumerBase, visitors to the Málaga Fair]
-
A.
mainFeederOf
Indicates that one entity serves as the primary source or supplier of resources, energy, or input to another entity.
-
B.
notableConsumer
Indicates that one entity is a prominent or significant user or buyer of another entity’s products, services, or resources.
-
C.
hasNotableConsumerBase
chosen
Indicates that an entity is recognized for having a significant or prominent group of consumers or users.
-
D.
consumes
Indicates that one entity eats, drinks, or otherwise uses up another entity as a resource or nourishment.
-
E.
mainBase
Indicates that one entity serves as the primary or central base or headquarters for another entity.
- 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_69ef96b8b8d88190bad5e4ae966bf14e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 27, 2026, 7:47 p.m.