Triple
T36042051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summer Street, Surrey |
E1042566
|
entity |
| Predicate | usedAsContrastTo |
P120686
|
FINISHED |
| Object | Florence |
—
|
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: Florence | Statement: [Summer Street, Surrey, usedAsContrastTo, Florence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsContrastTo Context triple: [Summer Street, Surrey, usedAsContrastTo, Florence]
-
A.
providesContrastWith
Indicates that one entity is used to highlight differences or distinctions when compared with another entity.
-
B.
contrastUse
chosen
Indicates that one entity is used in opposition or distinction to another to highlight differences between them.
-
C.
achievesContrast
Indicates that one entity creates or enhances a visual or conceptual difference relative to another entity.
-
D.
createsContrastIn
Indicates a relationship where one element is used to highlight or emphasize differences with another element within a given context.
-
E.
oftenContrastedWith
Indicates that one entity is frequently compared to another in a way that highlights their differences or opposing characteristics.
- 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_69f76e2d7e8c8190bac4e90734566799 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fec5c503808190bde0b1829ea43071 |
completed | May 9, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69fec535dd6c8190a6ab85201f5a04a9 |
completed | May 9, 2026, 5:25 a.m. |
Created at: May 3, 2026, 4:07 p.m.