Triple
T3052303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyclone Tracy |
E60397
|
entity |
| Predicate | landfallLocalTime |
P33470
|
FINISHED |
| Object | early hours of 1974-12-25 |
—
|
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: early hours of 1974-12-25 | Statement: [Cyclone Tracy, landfallLocalTime, early hours of 1974-12-25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landfallLocalTime Context triple: [Cyclone Tracy, landfallLocalTime, early hours of 1974-12-25]
-
A.
landfallLocation
Indicates the geographic location where a storm or similar weather system first makes landfall.
-
B.
earthquakeLocalTime
Indicates the local time at which an earthquake event occurred at its specific location.
-
C.
localTime
Indicates that a specific time value is expressed relative to a particular local time zone or locale, rather than in a universal or standardized time reference.
-
D.
impactTimeLocal
chosen
Indicates the specific local time at which an impact event occurs or is expected to occur.
-
E.
landingTimeUTC
Indicates the exact time, expressed in Coordinated Universal Time (UTC), at which an entity (such as an aircraft or spacecraft) completes its landing.
- 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_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. |
Created at: March 8, 2026, 3:01 p.m.