Triple
T3200009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manzanilla sherry |
E67026
|
entity |
| Predicate | fortifiedWith |
P46082
|
FINISHED |
| Object | grape spirit |
—
|
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: grape spirit | Statement: [Manzanilla sherry, fortifiedWith, grape spirit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fortifiedWith Context triple: [Manzanilla sherry, fortifiedWith, grape spirit]
-
A.
wasFortifiedBy
Indicates that a place or structure received defensive strengthening or fortification through the actions or resources of a specified agent or entity.
-
B.
isFortifiedCity
Indicates that a city is strengthened with defensive structures or fortifications, such as walls, ramparts, or similar protective works.
-
C.
reinforcedIn
Indicates that one entity is strengthened, supported, or made more robust within, or as a result of conditions in, another entity or context.
-
D.
impregnatedBy
Indicates that one entity has caused another entity to become pregnant.
-
E.
hasFortifications
Indicates that one entity possesses or is equipped with defensive structures or fortification works associated with it.
- F. None of above. chosen
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_69ad8589bd988190afa7ed2bdffb7b33 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada9ad4b1c8190bc6ad0f025f238c8 |
completed | March 8, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69ad9e05e4f48190adbe4366cdba2349 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f9259c8190afbc5ad0fa55436b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:07 p.m.