Triple
T26376619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACCU conference |
E660916
|
entity |
| Predicate | hasSubmissionProcess |
P67136
|
FINISHED |
| Object | call for 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: call for papers | Statement: [ACCU conference, hasSubmissionProcess, call for papers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubmissionProcess Context triple: [ACCU conference, hasSubmissionProcess, call for papers]
-
A.
hasSubmissionPolicy
chosen
Indicates that an entity is associated with a specific set of rules or conditions governing how submissions to it must be made.
-
B.
hasGrantApplicationProcess
Indicates that an entity has a defined procedure or set of steps for submitting and processing grant applications.
-
C.
submissionStatus
Indicates the current state or phase of a submitted item within a review or processing workflow.
-
D.
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.
-
E.
hasAppointmentProcess
Indicates that there is a defined procedure or workflow for scheduling, managing, or conducting an appointment between parties.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 26, 2026, 11:01 p.m.