Triple
T8410424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherry Esplanade |
E198607
|
entity |
| Predicate | bestKnownForSeason |
P80837
|
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: [Cherry Esplanade, bestKnownForSeason, spring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestKnownForSeason Context triple: [Cherry Esplanade, bestKnownForSeason, spring]
-
A.
seasonBestKnownFor
chosen
Indicates the work, achievement, or characteristic for which a particular season is most notably recognized.
-
B.
notableSeason
Indicates that a particular season is especially significant or noteworthy in relation to an entity (such as a person, team, or series).
-
C.
playedInSeason
Indicates that an entity (such as a player or participant) took part in or was active during a specific season.
-
D.
playsInSeason
Indicates that an entity participates or performs in a specific season of an ongoing series, competition, or event.
-
E.
laterKnownFor
Indicates that an entity became recognized or notable for something at a later time than the context or event currently being referred to.
- 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb83dec1f08190ae08719e860b29fa |
completed | March 31, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69cb70d473dc8190af8ea81ee5aa970d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:05 p.m.