Triple
T35806025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Levesque |
E1035101
|
entity |
| Predicate | hallOfFameAsMemberOf |
P184129
|
FINISHED |
| Object | D-Generation X |
—
|
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: D-Generation X | Statement: [Paul Levesque, hallOfFameAsMemberOf, D-Generation X]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hallOfFameAsMemberOf Context triple: [Paul Levesque, hallOfFameAsMemberOf, D-Generation X]
-
A.
inHallOfFame
Indicates that an entity has been formally inducted into a recognized Hall of Fame.
-
B.
hallOfFameConnection
Indicates a relationship where an entity is connected to a hall of fame, such as by being inducted, nominated, or otherwise formally associated with it.
-
C.
hasHallOfFameParent
Indicates that an entity has a parent who is a member of a Hall of Fame.
-
D.
hallOfFameAssociation
Indicates that an entity is formally associated with a hall of fame, such as through induction, nomination, or recognition.
-
E.
hallOfFameRole
Indicates the specific role, capacity, or category under which an entity is inducted into a hall of fame.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:06 p.m.