Triple
T22178032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scientific Reports |
E548096
|
entity |
| Predicate | hasOpenDataPolicy |
P10529
|
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: [Scientific Reports, hasOpenDataPolicy, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpenDataPolicy Context triple: [Scientific Reports, hasOpenDataPolicy, yes]
-
A.
dataPolicy
chosen
Indicates that one entity defines or governs how data related to another entity is collected, used, stored, or shared.
-
B.
hasPartOpenToPublic
Indicates that some portion or component of an entity is accessible for use or visitation by the general public.
-
C.
hasPublicationPolicy
Indicates that an entity is associated with or governed by a specific policy regarding the creation, review, or dissemination of publications.
-
D.
hasPolicySupport
Indicates that one entity provides endorsement, backing, or approval for a specific policy associated with another entity.
-
E.
hasPublicSpacePolicy
Indicates that an entity has an established policy governing the use, management, or regulation of public spaces.
- 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_69e11e3d53f88190a2b690e3f25bb062 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a6dd5a081908035e81c068d8d5a |
completed | April 28, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:34 p.m.