Triple
T5975479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brazilian Venice |
E132974
|
entity |
| Predicate | hasNotableComparison |
P44207
|
FINISHED |
| Object | Venice’s canals and bridges |
—
|
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: Venice’s canals and bridges | Statement: [Brazilian Venice, hasNotableComparison, Venice’s canals and bridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableComparison Context triple: [Brazilian Venice, hasNotableComparison, Venice’s canals and bridges]
-
A.
hasNotableDelta
Indicates that there is a significant or noteworthy change or difference between two compared entities or states.
-
B.
notableComparison
chosen
Indicates that one entity is being compared to another in a way that is especially significant, remarkable, or worthy of note.
-
C.
hasNotableMetric
Indicates that an entity is associated with a specific metric or measurement that is considered significant or noteworthy in its context.
-
D.
hasNotableReference
Indicates that one entity makes a significant or noteworthy mention of, or allusion to, another entity.
-
E.
hasNotableVersion
Indicates that an entity has a specific version or variant that is particularly significant, distinguished, or noteworthy compared to other versions.
- 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_69c0086deab081908550159ca23eec9b |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04dc2243c8190bd3488e7b24af985 |
completed | March 22, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c049dcb3c081908ccc9b4d4b210229 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:04 p.m.