Triple
T35242123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ronald Bixby |
E1017553
|
entity |
| Predicate | useOfStageName |
P182651
|
FINISHED |
| Object | He was better known by his stage name Skip Young |
—
|
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: He was better known by his stage name Skip Young | Statement: [Ronald Bixby, useOfStageName, He was better known by his stage name Skip Young]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useOfStageName Context triple: [Ronald Bixby, useOfStageName, He was better known by his stage name Skip Young]
-
A.
usedStageNameUntil
Indicates that an entity used a particular stage name up to a specified point in time, after which it was no longer used.
-
B.
usesStageNameFormat
Indicates that an entity’s stage name follows or conforms to a particular naming format or pattern.
-
C.
usedStage
Indicates that an entity made use of a particular stage or phase within a process, workflow, or lifecycle.
-
D.
usesStageType
Indicates that one entity employs or operates with a particular type or category of stage.
-
E.
usedAsStageNameBySomeBearers
Indicates that the name is employed as a stage name by at least some of its bearers.
- 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_69f76de235048190b990070c23c51b6b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7904a770481908ef3f788e51e8dba |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78f629d508190b755848162c4e101 |
completed | May 3, 2026, 6:09 p.m. |
Created at: May 3, 2026, 4:02 p.m.