Triple
T35558511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACM Gordon Bell Prize |
E1027568
|
entity |
| Predicate | submissionVenue |
P53492
|
FINISHED |
| Object | SC Conference technical program |
—
|
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: SC Conference technical program | Statement: [ACM Gordon Bell Prize, submissionVenue, SC Conference technical program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: submissionVenue Context triple: [ACM Gordon Bell Prize, submissionVenue, SC Conference technical program]
-
A.
publishingVenue
chosen
Indicates the venue (such as a journal, conference, or publisher) where a work is formally published.
-
B.
submissionSystem
Indicates a relationship where something is provided or turned in through a designated system or platform for receiving submissions.
-
C.
conferencePlacement
Indicates that an entity has been assigned a specific placement, ranking, or position within a conference or similar organized event.
-
D.
submissionBy
Indicates that one entity is the submitter or originator of a particular submission associated with another entity.
-
E.
submissionWith
Indicates that one entity is submitted together with, or as part of the same submission as, another entity.
- 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_69f76e014fd481909e9f04ac603a2aa9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.