Triple
T139948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE Transactions on Communications |
E2828
|
entity |
| Predicate | hasPublisherType |
P641
|
FINISHED |
| Object | professional association |
—
|
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: professional association | Statement: [IEEE Transactions on Communications, hasPublisherType, professional association]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublisherType Context triple: [IEEE Transactions on Communications, hasPublisherType, professional association]
-
A.
hasPublisher
Indicates that an entity is published or issued by a specific publisher.
-
B.
publisherType
chosen
Indicates the classification or category of a publisher in relation to a published work or entity.
-
C.
hasPublication
Indicates that an entity is associated with or responsible for a specific publication.
-
D.
hasSisterPublication
Indicates that one publication is related to another as a sister publication, typically under the same parent organization or closely associated in scope or branding.
-
E.
publishingModel
Indicates the method or framework by which content is produced, distributed, and 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257c679d88190bc71775dab2cfc64 |
completed | Feb. 28, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69a2565426c08190aab68e34a6a2d60e |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.