Triple
T10935543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monarch |
E258321
|
entity |
| Predicate | relationshipWithGodzilla |
P96718
|
FINISHED |
| Object | ally |
—
|
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: ally | Statement: [Monarch, relationshipWithGodzilla, ally]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipWithGodzilla Context triple: [Monarch, relationshipWithGodzilla, ally]
-
A.
roleInMonsterVerse
Indicates that an entity has a specific role or function within the MonsterVerse franchise or universe.
-
B.
associatedWithGod
Indicates a relationship in which an entity is linked, related, or connected in some meaningful way to a god or deity.
-
C.
relationshipToDeities
Indicates how an entity is connected or related to one or more deities, such as through worship, lineage, role, or status.
-
D.
relatedNameOfGod
Indicates that one entity is a name, title, or designation that refers to or is associated with God.
-
E.
opusRelationship
Indicates a relationship between creative works (opuses), such as versions, adaptations, or parts within a larger compositional whole.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770aee178819082c1671a37ff7d82 |
completed | April 9, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_69d72e816a98819096d6c10dfb88a66a |
completed | April 9, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69d7322370648190ba14cdd6fb4cdcb0 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:23 p.m.