Triple
T8679898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Sydney |
E206010
|
entity |
| Predicate | featuredKaiju |
P18264
|
FINISHED |
| Object | kaiju |
—
|
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: kaiju | Statement: [Battle of Sydney, featuredKaiju, kaiju]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredKaiju Context triple: [Battle of Sydney, featuredKaiju, kaiju]
-
A.
featuresMonster
chosen
Indicates that something includes or prominently presents a monster as part of its content or composition.
-
B.
superkingdom
Indicates the broadest taxonomic relationship in which one entity is classified as belonging to a particular superkingdom in the hierarchy of life.
-
C.
specialFeature
Indicates that an entity possesses a distinctive or noteworthy attribute, capability, or characteristic that sets it apart from others.
-
D.
notableGiant
Indicates that an entity is recognized as a giant of particular note, standing out for its exceptional size, influence, or significance relative to others of its kind.
-
E.
animalClassFeatured
Indicates that a particular animal class is highlighted or prominently presented in relation to something (such as content, a display, or a context).
- 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.