Triple
T29768162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Cross region |
E753971
|
entity |
| Predicate | visibleBestInSeason |
P150588
|
FINISHED |
| Object | autumnInSouthernHemisphere |
—
|
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: autumnInSouthernHemisphere | Statement: [Southern Cross region, visibleBestInSeason, autumnInSouthernHemisphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visibleBestInSeason Context triple: [Southern Cross region, visibleBestInSeason, autumnInSouthernHemisphere]
-
A.
visibleBestInMonth
Indicates that something is the most prominent or highest-ranked among visible items within a given month.
-
B.
bestOfSeries
Indicates that one entity is the winner or top performer within a defined series or set of related items or events.
-
C.
bestKnownSeason
Indicates the season for which an entity is most prominently or widely recognized.
-
D.
isVisibleBestIn
chosen
Indicates that an entity is considered the most visible or prominent within a specified context or set.
-
E.
popularSeason
Indicates that a particular season is widely liked, favored, or frequently chosen by many people.
- 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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f6745f8354819085a81de5c32dd49e |
completed | May 2, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 8:39 p.m.