Triple
T31107079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titans (MonsterVerse) |
E792822
|
entity |
| Predicate | alphaMember |
P27891
|
FINISHED |
| Object | Godzilla (MonsterVerse) |
—
|
NE NERFINISHED |
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: Godzilla (MonsterVerse) | Statement: [Titans (MonsterVerse), alphaMember, Godzilla (MonsterVerse)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alphaMember Context triple: [Titans (MonsterVerse), alphaMember, Godzilla (MonsterVerse)]
-
A.
affMember
Indicates that an entity is affiliated as a member of another entity, such as an organization, group, or institution.
-
B.
activeMember
Indicates that an entity currently participates in and holds membership status within a group, organization, or community.
-
C.
membershipIn
chosen
Indicates that an entity belongs to, is part of, or holds membership in a particular group, organization, or collection.
-
D.
memberFrom
Indicates that an entity is a member originating from, or associated with, a particular source, group, or location.
-
E.
creditedMember
Indicates that a particular member is formally acknowledged or recognized as having contributed to or been responsible for something.
- 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:03 p.m.