Triple
T1286445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proceedings of Meetings on Acoustics |
E27443
|
entity |
| Predicate | hasPublicationModel |
P628
|
FINISHED |
| Object | article-based publishing |
—
|
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: article-based publishing | Statement: [Proceedings of Meetings on Acoustics, hasPublicationModel, article-based publishing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicationModel Context triple: [Proceedings of Meetings on Acoustics, hasPublicationModel, article-based publishing]
-
A.
hasPublication
Indicates that an entity is associated with or responsible for a specific publication.
-
B.
hasReleaseModel
Indicates the type or strategy of release associated with an entity, such as how or under what model it is made available.
-
C.
publishingModel
chosen
Indicates the method or framework by which content is produced, distributed, and made publicly available.
-
D.
hasPublisher
Indicates that an entity is published or issued by a specific publisher.
-
E.
isPublished
Indicates that an item has been formally made available to the public through some publishing process.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0b85eb48190a8b61dc397fa6390 |
completed | March 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69a4bee276d8819092f71c5a1140bb61 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.