Triple
T24027210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vuelta Arriba |
E594996
|
entity |
| Predicate | productDestination |
P127496
|
FINISHED |
| Object | cigar factories |
—
|
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: cigar factories | Statement: [Vuelta Arriba, productDestination, cigar factories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productDestination Context triple: [Vuelta Arriba, productDestination, cigar factories]
-
A.
destinedFor
Indicates that one entity is intended, assigned, or meant to be used for, received by, or directed toward another entity or purpose.
-
B.
tradeDestination
chosen
Indicates the location or entity to which goods, services, or financial assets are sent or directed as part of a trade transaction.
-
C.
territoryOfDestination
Indicates that a specified territory is the destination or endpoint location associated with an action, movement, or relation.
-
D.
oreShippedTo
Indicates that ore is transported or delivered from one location or entity to another.
-
E.
primaryFreightDestination
Indicates the main location to which freight is intended to be shipped or delivered.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d76c083c819090784ecb42effbae |
completed | April 29, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:54 p.m.