Triple
T38255472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canale Vena |
E1017776
|
entity |
| Predicate | hasSimilarTo |
P94757
|
FINISHED |
| Object | Venice canals |
—
|
NE NERFINISHED |
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: Venice canals | Statement: [Canale Vena, hasSimilarTo, Venice canals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSimilarTo Context triple: [Canale Vena, hasSimilarTo, Venice canals]
-
A.
hasSimilarityTo
chosen
Indicates that one entity shares common characteristics, features, or qualities with another entity to a notable degree.
-
B.
lessSimilarTo
Indicates that one entity is considered to share fewer similarities or a weaker resemblance with another entity compared to some reference or alternative.
-
C.
hasSyntaxSimilarTo
Indicates that one entity’s syntax closely resembles or matches the syntactic structure or form of another entity.
-
D.
namedForSimilarityTo
Indicates that one entity is given its name because of a perceived resemblance or likeness to another entity.
-
E.
hasPowerSimilarTo
Indicates that one entity possesses a level or type of power comparable to that of 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_69f76de33e4481909099fa812709bd42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe9dfaa2d08190b2084f63f842eb6b |
completed | May 9, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69fe9bba947c81908b0b2b92a4d19b37 |
completed | May 9, 2026, 2:28 a.m. |
Created at: May 3, 2026, 4:30 p.m.