Triple
T20327459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caldwell 106 |
E492376
|
entity |
| Predicate | bestObservedInSeason |
P114970
|
FINISHED |
| Object | Southern 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: Southern spring | Statement: [Caldwell 106, bestObservedInSeason, Southern spring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestObservedInSeason Context triple: [Caldwell 106, bestObservedInSeason, Southern spring]
-
A.
bestKnownSeason
chosen
Indicates the season for which an entity is most prominently or widely recognized.
-
B.
bestObservedWith
Indicates that one entity is most effectively or appropriately observed, detected, or measured when used or considered together with another specified entity.
-
C.
wonSeasonOf
Indicates that one entity emerged as the overall winner of a particular season of a competition, show, or series involving the other entity.
-
D.
bestSeasonResultYear
Indicates the year in which an entity achieved its best season result.
-
E.
notableSeason
Indicates that a particular season is especially significant or noteworthy in relation to an entity (such as a person, team, or series).
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677e513608190b70527cd9f4d5da3 |
completed | April 20, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:21 a.m.