Triple
T36095553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Behemoth |
E1044047
|
entity |
| Predicate | awakeningEvent |
P184672
|
FINISHED |
| Object | global Titan awakening in Godzilla: King of the Monsters |
—
|
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: global Titan awakening in Godzilla: King of the Monsters | Statement: [Behemoth, awakeningEvent, global Titan awakening in Godzilla: King of the Monsters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awakeningEvent Context triple: [Behemoth, awakeningEvent, global Titan awakening in Godzilla: King of the Monsters]
-
A.
awakensBy
Indicates that one entity causes another entity to wake up from sleep or inactivity.
-
B.
awakensIn
Indicates that one entity comes out of sleep or becomes conscious while located within or inside another entity.
-
C.
awakensBefore
Indicates that one entity wakes up earlier in time than another entity.
-
D.
ageOfAwakening
Indicates the specific age at which an entity becomes aware, conscious, or begins its significant period of activity or development.
-
E.
observedEvent
Indicates that an entity has perceived, detected, or recorded the occurrence of a particular event.
- 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_69f76e32d60c8190ba781ffaaab4aa3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b3e0f1c88190985feab6cee8b05e |
completed | May 3, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:08 p.m.