Triple
T17479189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S.K. Club |
E425612
|
entity |
| Predicate | targetMemberProfile |
P127611
|
FINISHED |
| Object | social elites |
—
|
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: social elites | Statement: [S.K. Club, targetMemberProfile, social elites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetMemberProfile Context triple: [S.K. Club, targetMemberProfile, social elites]
-
A.
participantProfile
Indicates that an entity serves as the profile or descriptive record associated with a particular participant in an event, activity, or process.
-
B.
profileType
Indicates the specific category or role classification assigned to a profile within a system.
-
C.
profileDirectory
Indicates the directory path where a user's or application's profile data is stored or managed.
-
D.
visitorProfile
Indicates a relationship where a profile encapsulates information or attributes associated with a particular visitor.
-
E.
throughMember
Indicates that a relationship or action occurs by means of, or is mediated or facilitated by, a particular member of a group or organization.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451be5fd08190aeaa12b3a6d6c6d4 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:48 a.m.