Triple
T34543117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JSTOR |
E886854
|
entity |
| Predicate | hasOpenAccessContent |
P31861
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [JSTOR, hasOpenAccessContent, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpenAccessContent Context triple: [JSTOR, hasOpenAccessContent, yes]
-
A.
hasPartOpenToPublic
Indicates that some portion or component of an entity is accessible for use or visitation by the general public.
-
B.
contentAccess
Indicates that one entity is permitted to retrieve, view, or otherwise use the content provided or controlled by another entity.
-
C.
isFreeToRead
chosen
Indicates that access to the referenced content or resource does not require payment and can be read without cost.
-
D.
hasEditorialContent
Indicates that an entity includes or is associated with editorially created or curated content, such as articles, commentary, or opinion pieces.
-
E.
hasDigitalAccess
Indicates that an entity has the ability or permission to use or access digital resources, services, or information.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 1, 2026, 2:02 a.m.