Triple
T11650325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AER |
E276883
|
entity |
| Predicate | hasPublisherPolicy |
P82624
|
FINISHED |
| Object | allows self-archiving of some versions |
—
|
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: allows self-archiving of some versions | Statement: [AER, hasPublisherPolicy, allows self-archiving of some versions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublisherPolicy Context triple: [AER, hasPublisherPolicy, allows self-archiving of some versions]
-
A.
hasPublicationPolicy
Indicates that an entity is associated with or governed by a specific policy regarding the creation, review, or dissemination of publications.
-
B.
hasPublisher
Indicates that an entity is published or issued by a specific publisher.
-
C.
hasPolicySupport
Indicates that one entity provides endorsement, backing, or approval for a specific policy associated with another entity.
-
D.
hasPolicyPage
chosen
Indicates that an entity maintains or is associated with a dedicated policy page, typically outlining rules, terms, or guidelines.
-
E.
hasPolicyStatus
Indicates that an entity is associated with a policy and specifies the current status or state of that policy.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a2cea9308190a13f7dd995ea07a4 |
completed | April 10, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.