Triple
T655268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabrosa |
E11633
|
entity |
| Predicate | hasTraditionalProduct |
P3585
|
FINISHED |
| Object | Port wine (production area context) |
—
|
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: Port wine (production area context) | Statement: [Sabrosa, hasTraditionalProduct, Port wine (production area context)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalProduct Context triple: [Sabrosa, hasTraditionalProduct, Port wine (production area context)]
-
A.
hasProduct
chosen
Indicates that an entity possesses, offers, or is associated with a particular product.
-
B.
hasTraditionalSymbol
Indicates that something is associated with or represented by a conventional or culturally established symbol.
-
C.
traditionallyOneOf
Indicates that something is customarily or historically considered to belong to a specific set, category, or group.
-
D.
hasLegacy
Indicates that an entity leaves behind a lasting impact, influence, or inheritance that continues to exist or be recognized over time.
-
E.
hasTrade
Indicates a relationship where one entity engages in or maintains a commercial exchange or trading activity with 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f4d57688190a9515ac494a97b22 |
completed | March 1, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69a49d121cec81909986c91291bb4ca8 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.