Triple
T32607531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Probability Surveys |
E833559
|
entity |
| Predicate | hasSubmissionGuidelines |
P67136
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Probability Surveys, hasSubmissionGuidelines, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubmissionGuidelines Context triple: [Probability Surveys, hasSubmissionGuidelines, yes]
-
A.
hasGuideline
Indicates that one entity is governed, informed, or constrained by a rule, standard, or recommended procedure provided by another entity.
-
B.
hasSubmissionPolicy
chosen
Indicates that an entity is associated with a specific set of rules or conditions governing how submissions to it must be made.
-
C.
submissionBasis
Indicates the basis, criteria, or grounds on which something is submitted or filed (e.g., a document, application, or claim).
-
D.
acceptsSubmissionsFrom
Indicates that one entity receives and is willing to consider submissions (such as content, proposals, or applications) originating from another entity.
-
E.
submissionMedium
Indicates the medium or channel through which something (such as a document, work, or request) is submitted or delivered.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff1ba8694481909ceb36f26ca85612 |
completed | May 9, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69ff1b27f0f08190a9e74308c5b3d1ba |
completed | May 9, 2026, 11:31 a.m. |
Created at: May 1, 2026, 1:05 a.m.