Triple
T1471816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acoustics Today |
E27150
|
entity |
| Predicate | publishingGoal |
P24455
|
FINISHED |
| Object | to provide accessible articles on acoustics |
—
|
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: to provide accessible articles on acoustics | Statement: [Acoustics Today, publishingGoal, to provide accessible articles on acoustics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publishingGoal Context triple: [Acoustics Today, publishingGoal, to provide accessible articles on acoustics]
-
A.
publishingPurpose
chosen
Indicates the intended goal or reason for which something is being published.
-
B.
publishingModel
Indicates the method or framework by which content is produced, distributed, and made publicly available.
-
C.
publishesFor
Indicates that one entity issues, releases, or makes content publicly available on behalf of, or in service of, another entity.
-
D.
publishingPlatform
Indicates that one entity serves as the medium or service through which another entity is published or made publicly available.
-
E.
publishingForm
Indicates the medium or format in which something is published or made publicly available.
- 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_69a496d25d6881909dbd84f86d763992 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c5db55948190ae5262a70a161b87 |
completed | March 1, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69a4c48350d88190a81bd149103f93e3 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:01 p.m.