Triple
T25717915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Research Libraries Group |
E644908
|
entity |
| Predicate | member type |
P4027
|
FINISHED |
| Object | research libraries |
—
|
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: research libraries | Statement: [Research Libraries Group, member type, research libraries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: member type Context triple: [Research Libraries Group, member type, research libraries]
-
A.
memberCategory
chosen
Indicates that an entity belongs to or is classified under a specific category or group.
-
B.
memberFrom
Indicates that an entity is a member originating from, or associated with, a particular source, group, or location.
-
C.
membershipBy
Indicates that one entity holds membership or belongs to a group, organization, or collection defined by another entity.
-
D.
membershipBased
Indicates that access, participation, or inclusion in something is conditional on holding a membership or belonging to a defined group.
-
E.
membershipField
Indicates that one entity serves as a field or attribute capturing the membership status or association of another entity within a group, organization, 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 21, 2026, 9:48 p.m.