Triple
T8679918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Sydney |
E206010
|
entity |
| Predicate | chronologyWithinUniverse |
P81795
|
FINISHED |
| Object | later stages of the Kaiju War |
—
|
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: later stages of the Kaiju War | Statement: [Battle of Sydney, chronologyWithinUniverse, later stages of the Kaiju War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologyWithinUniverse Context triple: [Battle of Sydney, chronologyWithinUniverse, later stages of the Kaiju War]
-
A.
chronologyOf
Indicates that one entity represents the temporal ordering, sequence, or historical timeline of events or states associated with another entity.
-
B.
chronologyWithinMythos
chosen
Indicates that one event, story, or element occurs at a specific position or order within the internal timeline of a particular mythos or fictional universe.
-
C.
chronologyEstablishedBy
Indicates that the temporal order or dating of events, objects, or periods is determined or defined by a specified source, method, or authority.
-
D.
chronologyNote
Indicates a note that explains or clarifies the temporal order, dating, or sequence of related events or records.
-
E.
chronologyStart
Indicates the point in time at which a sequence, event, or temporal record begins.
- 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_69ca835379688190aa06b9d98e684d58 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4ae6d19c8190be003f7901c0468d |
completed | March 31, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69cc4567b5c881908d9ec5dcfc783fac |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:32 p.m.