Triple
T18158791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IACR Cryptology ePrint Archive |
E434700
|
entity |
| Predicate | hasSubmissionModel |
P67136
|
FINISHED |
| Object | author self-archiving |
—
|
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: author self-archiving | Statement: [IACR Cryptology ePrint Archive, hasSubmissionModel, author self-archiving]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubmissionModel Context triple: [IACR Cryptology ePrint Archive, hasSubmissionModel, author self-archiving]
-
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.
hasReleaseModel
Indicates the type or strategy of release associated with an entity, such as how or under what model it is made available.
-
C.
hasModelStatus
Indicates that an entity is assigned a particular model-related state or condition, such as its current phase, validity, or operational status within a modeling context.
-
D.
hasSubsummit
Indicates that one entity holds a subordinate or lower-ranked position under another entity within a hierarchical structure.
-
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.
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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dec02d9c81909ac6203b7d59c405 |
completed | April 19, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:30 a.m.