Triple
T18845800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C6 |
E460908
|
entity |
| Predicate | membershipByAppointment |
P133161
|
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: [C6, membershipByAppointment, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: membershipByAppointment Context triple: [C6, membershipByAppointment, true]
-
A.
membershipBy
Indicates that one entity holds membership or belongs to a group, organization, or collection defined by another entity.
-
B.
membershipApplicationOf
Indicates that one entity is a membership application that is submitted for or associated with another entity (typically the applicant or organization).
-
C.
membershipDecidedBy
Indicates that the determination of whether an entity is granted membership in a group, organization, or set is made by another specified entity or process.
-
D.
membershipIn
Indicates that an entity belongs to, is part of, or holds membership in a particular group, organization, or collection.
-
E.
enabledAppointmentOf
Indicates that one entity made it possible or authorized for another entity to be appointed to a role or position.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8ee96988190bf247b986777945c |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:56 a.m.