Triple
T28191794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skillibeng |
E716335
|
entity |
| Predicate | hasStageNameType |
P153527
|
FINISHED |
| Object | mononym |
—
|
LITERAL 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: mononym | Statement: [Skillibeng, hasStageNameType, mononym]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStageNameType Context triple: [Skillibeng, hasStageNameType, mononym]
-
A.
hasStageNameVariant
Indicates that an entity has an alternative or variant form of its stage name.
-
B.
hasStageType
Indicates that an entity is associated with, or classified by, a specific type or category of stage within a process, lifecycle, or workflow.
-
C.
hasFatherStageName
Indicates that an entity has a father whose commonly used or professional name is the specified stage name.
-
D.
hasMemberStageName
Indicates that an entity (such as a group or band) has a member whose professional or stage name is the specified value.
-
E.
usesStageNameFormat
chosen
Indicates that an entity’s stage name follows or conforms to a particular naming format or pattern.
- F. None of above.
Provenance (3 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: April 27, 2026, 10:25 p.m.