Triple
T35527529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul E. Dangerously |
E1026710
|
entity |
| Predicate | laterRingNameOfSamePerson |
P202289
|
FINISHED |
| Object | Paul Heyman |
—
|
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: Paul Heyman | Statement: [Paul E. Dangerously, laterRingNameOfSamePerson, Paul Heyman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRingNameOfSamePerson Context triple: [Paul E. Dangerously, laterRingNameOfSamePerson, Paul Heyman]
-
A.
originalRingName
Indicates the name originally used for a ring before any later changes or renamings.
-
B.
samePersonAs
Indicates that two referenced entities are in fact the very same individual, not just similar or related.
-
C.
usedRingNameUntil
Indicates that an entity used a particular ring name as their professional or public identity up until a specified time or event.
-
D.
usedAsRingNicknameBy
Indicates that something serves as a ring nickname that a particular person uses or is known by.
-
E.
associatedWithRing
Indicates that an entity has a connection or relationship with a specific ring, such as ownership, membership, or involvement.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a006ef900148190ba52daf566882a03 |
completed | May 10, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_6a006c76ae748190bfe466d7d17d321e |
completed | May 10, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_6a006ef80ce88190b5e3a2b261409d44 |
completed | May 10, 2026, 11:41 a.m. |
Created at: May 3, 2026, 4:04 p.m.