Triple
T1528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proceedings of the IRE |
E28
|
entity |
| Predicate | issn |
P132
|
FINISHED |
| Object | 0096-8390 |
—
|
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: 0096-8390 | Statement: [Proceedings of the IRE, issn, 0096-8390]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issn Context triple: [Proceedings of the IRE, issn, 0096-8390]
-
A.
issuedBy
Indicates that something (such as a document, order, or statement) has been formally created, authorized, or released by a particular agent or authority.
-
B.
hasPublication
Indicates that an entity is associated with or responsible for a specific publication.
-
C.
publicationYear
Indicates the specific calendar year in which a work was formally published or released.
-
D.
title
Indicates that one entity serves as the formal name or designation of another entity.
-
E.
submittedTo
Indicates that one entity has formally sent or presented something (such as a document, request, or work) to another entity for consideration, review, or processing.
- F. None of above. chosen
Provenance (4 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_69a22a285828819081a58308fb963df1 |
completed | Feb. 27, 2026, 11:35 p.m. |
| NER | Named-entity recognition | batch_69a2316d88a08190b2e03041674b5674 |
completed | Feb. 28, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69a230c3ee4481908216244c38aa8aef |
completed | Feb. 28, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69a2316cbe58819096cc036d6e3b103c |
completed | Feb. 28, 2026, 12:06 a.m. |
Created at: Feb. 27, 2026, 11:36 p.m.