Triple
T3052286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyclone Tracy |
E60397
|
entity |
| Predicate | occurredInSeason |
P45371
|
FINISHED |
| Object | 1974–75 Australian cyclone season |
—
|
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: 1974–75 Australian cyclone season | Statement: [Cyclone Tracy, occurredInSeason, 1974–75 Australian cyclone season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occurredInSeason Context triple: [Cyclone Tracy, occurredInSeason, 1974–75 Australian cyclone season]
-
A.
playedInSeason
Indicates that an entity (such as a player or participant) took part in or was active during a specific season.
-
B.
usedInSeason
Indicates that something (such as an item, strategy, or element) is utilized or appears within a particular season.
-
C.
playsInSeason
Indicates that an entity participates or performs in a specific season of an ongoing series, competition, or event.
-
D.
firstAiredInSeason
Indicates the specific season of a series in which an episode or content item was originally first broadcast or released.
-
E.
occurredIn
Indicates that an event or action took place within a specific location, context, or time frame.
- F. None of above. chosen
Provenance (4 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_69ad8578137c81908259dcb27c7d6d7c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9bf3c52c8190bbe8e5cb98c21715 |
completed | March 8, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69ad962195388190856013a2519c2b0f |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad9b272a408190ba0ce09bdeea76c9 |
completed | March 8, 2026, 3:52 p.m. |
Created at: March 8, 2026, 3:01 p.m.