Triple
T17312185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Academy members |
E420325
|
entity |
| Predicate | membershipByInvitation |
P126936
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Academy members, membershipByInvitation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: membershipByInvitation Context triple: [Academy members, membershipByInvitation, true]
-
A.
isInvited
Indicates that one entity has extended an invitation to another entity to participate in or attend something.
-
B.
invitesParticipationOf
Indicates that one entity actively requests or encourages another entity to take part in an activity, event, or process.
-
C.
membershipBy
Indicates that one entity holds membership or belongs to a group, organization, or collection defined by another entity.
-
D.
membershipApplicationOf
Indicates that one entity is a membership application that is submitted for or associated with another entity (typically the applicant or organization).
-
E.
mayReceiveInvitationTo
Indicates that one entity is allowed or eligible to be sent an invitation by another entity.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e439993bac8190a72f6af529bd7cce |
completed | April 19, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:43 a.m.