Triple
T17479186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S.K. Club |
E425612
|
entity |
| Predicate | membershipAccess |
P12367
|
FINISHED |
| Object | by invitation only |
—
|
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: by invitation only | Statement: [S.K. Club, membershipAccess, by invitation only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: membershipAccess Context triple: [S.K. Club, membershipAccess, by invitation only]
-
A.
membershipArea
Indicates the geographic or organizational area within which a membership is valid or applicable.
-
B.
membershipRequired
chosen
Indicates that access to or use of something is conditional on being a member of a specified group or organization.
-
C.
membershipPractice
Indicates a relationship where an entity engages in or applies specific practices, behaviors, or procedures associated with its membership in a group, organization, or category.
-
D.
membershipStatus
Indicates the current state or level of an entity’s participation or affiliation within a group, organization, or program.
-
E.
membershipBy
Indicates that one entity holds membership or belongs to a group, organization, or collection defined by another entity.
- 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_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. |
Created at: April 10, 2026, 5:48 a.m.