Triple
T7118796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perennial Border |
E165890
|
entity |
| Predicate | hasPrimarySeasonalInterest |
P1190
|
FINISHED |
| Object | spring |
—
|
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 | Statement: [Perennial Border, hasPrimarySeasonalInterest, spring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimarySeasonalInterest Context triple: [Perennial Border, hasPrimarySeasonalInterest, spring]
-
A.
hasSeasonalHighlight
Indicates that something features a notable or emphasized aspect during a particular season or time of year.
-
B.
hasSeasonalStatus
Indicates that an entity’s status, availability, or condition varies according to a particular season or time of year.
-
C.
hasSeasonalNature
Indicates that something exhibits characteristics, behavior, or occurrence patterns that vary according to specific seasons or times of the year.
-
D.
hasSeasonalParticipationIn
Indicates that an entity takes part in or is involved with another entity only during specific seasons or recurring seasonal periods.
-
E.
hasImportantSeason
chosen
Indicates that an entity experiences a particular season or time period that is especially significant or notable for it.
- 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_69c6888227bc8190a1394679e3116f90 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e61b8a288190a165ea25adfaaef5 |
completed | March 27, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c4f9788190830288d00cc37026 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:43 p.m.