Triple
T14464787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Eternal Spring |
E358677
|
entity |
| Predicate | seasonalDescription |
P14881
|
FINISHED |
| Object | eternal 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: eternal spring | Statement: [City of Eternal Spring, seasonalDescription, eternal spring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonalDescription Context triple: [City of Eternal Spring, seasonalDescription, eternal spring]
-
A.
hasSeasonalNature
Indicates that something exhibits characteristics, behavior, or occurrence patterns that vary according to specific seasons or times of the year.
-
B.
basedOnSeason
Indicates that something is determined, influenced, or derived according to a particular season or time of year.
-
C.
seasonMonths
Indicates the set of calendar months during which a given season occurs.
-
D.
seasonCharacterization
chosen
Indicates how a particular season is described, defined, or characterized in terms of its qualities or attributes.
-
E.
hasSeasonalHighlight
Indicates that something features a notable or emphasized aspect during a particular season or time of year.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91f6d4c08190a12e9a5901ee3508 |
completed | April 14, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.