Triple
T20929361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gouveio |
E515426
|
entity |
| Predicate | hasSynonymConfusion |
P2289
|
FINISHED |
| Object | similarity of name to Verdelho |
—
|
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: similarity of name to Verdelho | Statement: [Gouveio, hasSynonymConfusion, similarity of name to Verdelho]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSynonymConfusion Context triple: [Gouveio, hasSynonymConfusion, similarity of name to Verdelho]
-
A.
isNotSynonymOf
Indicates that two terms or expressions do not share the same or sufficiently similar meaning and therefore are not synonyms of each other.
-
B.
oftenConfusedWith
chosen
Indicates that one entity is frequently mistaken for or thought to be another due to similarity or ambiguity.
-
C.
hasDisambiguationNote
Indicates that there is an explanatory note used to distinguish this entity or term from other entities or terms with similar or identical names.
-
D.
synonym
Indicates that two terms have the same or nearly the same meaning in a given context.
-
E.
hasMultipleMeanings
Indicates that a term, symbol, or expression is associated with more than one distinct meaning or interpretation.
- 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_69e0b4fb431c8190b9d40e6a72f0cc87 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f6545f8c81908a8c2f0e8d7b060e |
completed | April 21, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:49 p.m.