Triple
T388903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Applied Physics Letters |
E8838
|
entity |
| Predicate | hasOpenAccessPolicy |
P1390
|
FINISHED |
| Object | hybrid |
—
|
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: hybrid | Statement: [Applied Physics Letters, hasOpenAccessPolicy, hybrid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpenAccessPolicy Context triple: [Applied Physics Letters, hasOpenAccessPolicy, hybrid]
-
A.
openAccessPolicy
chosen
Indicates that an entity has a policy allowing unrestricted or minimally restricted public access to its resources, content, or services.
-
B.
isOpenTo
Indicates that one entity is receptive, willing, or available to consider, accept, or engage with another entity or proposal.
-
C.
hasAccessTo
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
-
D.
hasAccessMode
Indicates the type or method of access that one entity is permitted to use with respect to another entity or resource.
-
E.
hasVisitorPolicy
Indicates that an entity has an established policy governing the presence, behavior, or permissions of visitors.
- 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec5988708190aa86d9460cecf050 |
completed | Feb. 28, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69a2e96960608190bdd342da9c5ddb5e |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.