Triple
T32607530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Probability Surveys |
E833559
|
entity |
| Predicate | hasCitationPolicy |
P182429
|
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, hasCitationPolicy, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCitationPolicy Context triple: [Probability Surveys, hasCitationPolicy, yes]
-
A.
hasCitationSystem
Indicates that one entity uses, follows, or is governed by a particular citation or referencing system defined by another entity.
-
B.
hasPeerReviewPolicy
Indicates that an entity maintains or is governed by a specific policy outlining how peer review is conducted.
-
C.
hasCitationInformation
Indicates that an entity is associated with specific citation details, such as source, reference, or bibliographic information.
-
D.
hasPublicationPolicy
Indicates that an entity is associated with or governed by a specific policy regarding the creation, review, or dissemination of publications.
-
E.
hasCitationStatus
Indicates the current citation-related state or condition assigned to a referenced work or source (e.g., cited, uncited, pending, or deprecated).
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f78d7211a48190bfb59c406f0bf12f |
completed | May 3, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78c6014e08190864785a4fe3e8e73 |
completed | May 3, 2026, 5:56 p.m. |
Created at: May 1, 2026, 1:05 a.m.