Triple
T35527441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sable Bomb |
E1026708
|
entity |
| Predicate | firstUsedInRingName |
P207032
|
FINISHED |
| Object | Sable |
E314537
|
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: Sable | Statement: [Sable Bomb, firstUsedInRingName, Sable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstUsedInRingName Context triple: [Sable Bomb, firstUsedInRingName, Sable]
-
A.
usedRingNameUntil
Indicates that an entity used a particular ring name as their professional or public identity up until a specified time or event.
-
B.
originalRingName
Indicates the name originally used for a ring before any later changes or renamings.
-
C.
usedAsRingNicknameBy
Indicates that something serves as a ring nickname that a particular person uses or is known by.
-
D.
usesRingNameDerivedFrom
Indicates that an entity uses a ring or stage name that is derived from another name or source entity.
-
E.
hasRingName
Indicates that an entity is associated with, or designated by, a specific ring name.
- F. None of above. chosen
Provenance (5 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_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3885da3e24819097bf710947d95cc6 |
completed | June 22, 2026, 12:46 a.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:04 p.m.