Triple
T232867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Conference on Distributed Computing Systems |
E4444
|
entity |
| Predicate | submissionType |
P10169
|
FINISHED |
| Object | research papers |
—
|
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: research papers | Statement: [International Conference on Distributed Computing Systems, submissionType, research papers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: submissionType Context triple: [International Conference on Distributed Computing Systems, submissionType, research papers]
-
A.
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.
-
B.
inscription
Indicates that text has been written, carved, or engraved onto a surface or object.
-
C.
subtitle
Indicates that one work serves as a secondary or explanatory title to another, typically appearing beneath the main title.
-
D.
dateOfSubmission
Indicates the specific date on which something (such as a document, application, or assignment) was formally submitted.
-
E.
typeOfSupport
Indicates the kind or category of assistance, help, or backing provided in a given context.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25f14f72081908182e76300b59358 |
completed | Feb. 28, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69a25b5c8c888190b5544e687736b373 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25f1450f08190872bcf58a32d506b |
completed | Feb. 28, 2026, 3:20 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.