Triple
T10846447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACM Transactions on Database Systems |
E256020
|
entity |
| Predicate | publisherField |
P1753
|
FINISHED |
| Object | computing |
—
|
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: computing | Statement: [ACM Transactions on Database Systems, publisherField, computing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherField Context triple: [ACM Transactions on Database Systems, publisherField, computing]
-
A.
publisherOfWorkAppearingIn
Indicates that an entity is the publisher responsible for issuing a work in which another specified work appears (e.g., as part of a collection, volume, or compilation).
-
B.
fieldOfPublication
chosen
Indicates the academic or topical area in which a work is published.
-
C.
publisherType
Indicates the classification or category of a publisher in relation to a published work or entity.
-
D.
publisherAbbreviation
Indicates that one entity is an abbreviated or shortened form of the name of a publisher entity.
-
E.
publishingOrganization
Indicates the organization responsible for issuing or making the referenced work 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d750d132e081909c977b3dc4110ca4 |
completed | April 9, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d70d2b51448190bae748ed6c23edde |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:20 p.m.