Triple
T4391661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newspaper and Current Periodical Reading Room |
E99376
|
entity |
| Predicate | intendedForUserGroup |
P53533
|
FINISHED |
| Object | researchers |
—
|
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: researchers | Statement: [Newspaper and Current Periodical Reading Room, intendedForUserGroup, researchers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedForUserGroup Context triple: [Newspaper and Current Periodical Reading Room, intendedForUserGroup, researchers]
-
A.
usedByGroup
chosen
Indicates that something is utilized or employed by a particular group or collective entity.
-
B.
hasUserGroup
Indicates that a user is associated with, belongs to, or is a member of a specific user group.
-
C.
belongsToGroup
Indicates that an entity is a member of, or is included within, a particular group or collection.
-
D.
primaryUserGroup
Indicates the main or default user group to which a user is primarily assigned or associated.
-
E.
grantedTo
Indicates that a right, permission, or resource has been formally given or assigned by one party to another.
- 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35285592881909fcdea225a655950 |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f572efc8190bad1e5078cbcb75a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:19 p.m.