Triple
T2288730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Top Social Artist |
E51453
|
entity |
| Predicate | eligibleEntities |
P15579
|
FINISHED |
| Object | solo artists |
—
|
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: solo artists | Statement: [Top Social Artist, eligibleEntities, solo artists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibleEntities Context triple: [Top Social Artist, eligibleEntities, solo artists]
-
A.
eligibleMembers
chosen
Indicates that certain entities meet the required criteria or conditions to be considered eligible members of a specified group or category.
-
B.
eligibleHolders
Indicates which entities are permitted or qualified to hold or possess a given item, right, or role.
-
C.
eligibleFrom
Indicates that a subject becomes or is considered eligible starting from a specified point in time or condition.
-
D.
eligibleBody
Indicates that an entity qualifies as an appropriate or permitted body (e.g., organization or institution) to participate in or be subject to a specified relationship or action.
-
E.
memberEntities
Indicates that certain entities belong to, or are included as members within, a larger group or collection.
- 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_69a88b09c644819090b503456d96bf70 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc2497ce881909b05eb9cec67d9e7 |
completed | March 7, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_69abbdbb9e4c819085fc588626ec7c09 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.