Triple
T31110426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Nexus |
E792927
|
entity |
| Predicate | notableMemberLaterRingName |
P202289
|
FINISHED |
| Object | Ryback |
E1631083
|
NE 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: Ryback | Statement: [The Nexus, notableMemberLaterRingName, Ryback]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMemberLaterRingName Context triple: [The Nexus, notableMemberLaterRingName, Ryback]
-
A.
notableMemberCommonName
Indicates that the object is the commonly used or well-known name of a notable member associated with the subject.
-
B.
laterRingNameOfSamePerson
chosen
Indicates that the second ring name is a later alias or stage name used by the same person as the first ring name.
-
C.
notableCharacterName
Indicates that the subject has a notable or significant character whose name is given by the object.
-
D.
usedAsRingNicknameBy
Indicates that something serves as a ring nickname that a particular person uses or is known by.
-
E.
notableMemberBirthName
Indicates the birth name of a notable member associated with an entity.
- F. None of above.
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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2938b2cc548190be5001e2c42012ba |
completed | June 10, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:04 p.m.