Triple
T1246090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Backs, Cambridge |
E26767
|
entity |
| Predicate | notableSeasonalFeature |
P14881
|
FINISHED |
| Object | spring blossom |
—
|
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: spring blossom | Statement: [The Backs, Cambridge, notableSeasonalFeature, spring blossom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSeasonalFeature Context triple: [The Backs, Cambridge, notableSeasonalFeature, spring blossom]
-
A.
notableSeason
Indicates that a particular season is especially significant or noteworthy in relation to an entity (such as a person, team, or series).
-
B.
seasonCharacterization
chosen
Indicates how a particular season is described, defined, or characterized in terms of its qualities or attributes.
-
C.
hasSeasonalPattern
Indicates that the occurrence, intensity, or characteristics of something regularly vary according to a recurring seasonal cycle.
-
D.
hasImportantSeason
Indicates that an entity experiences a particular season or time period that is especially significant or notable for it.
-
E.
season
Indicates that an entity participates in, is associated with, or occurs during a particular season or seasonal period.
- 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_69a4948689d08190b3a4a3f388c02148 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf65c41c8190b4c65e015d1264c0 |
completed | March 1, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69a4bb696a38819095845c84f0241287 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.